CVE-2026-81322

LowCVSS 2.1

Published: 30/08/2026(UTC)Translated: 31/08/2026(UTC)NVD NIST

Summary

Vulnerability in ash_cloak allows anyone with access to logs, error trackers, or crash reports, or anyone who can trigger a validation error, to recover the plaintext of an encrypted field. The argument carrying plaintext is not marked as sensitive, leading to its exposure in error messages and logs.

Risk Assessment

The organization may expose sensitive data in logs and error reports, potentially leading to information leakage.

Recommendation

Update ash_cloak to version 0.4.0 or later to fix the vulnerability.

Other vulnerabilities in ash_cloak

CVE-2026-81319Medium
Deserialization vulnerability in ash_cloak allows an attacker who can influence encrypted column bytes to crash the BEAM node via unbounded atom creation or decompression bomb during decryption. Unsafe deserialization without :safe option causes atom leak and compressed data inflation.

Original NVD description (English source)

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in ash-project ash_cloak allows anyone with access to logs, error trackers, or crash reports, or anyone who can trigger a validation error, to recover the plaintext of a field the library encrypts. AshCloak.Transformers.SetUpEncryption removes each cloaked attribute from the action's accept list and adds an action argument that carries the plaintext into the encryption change. That argument is built with sensitive?: attr.sensitive?, inheriting the flag from the source attribute, so a cloaked attribute declared without sensitive? true produces a non-sensitive argument. It is the only place the cleartext value lives, and the one place Ash will not redact: it appears verbatim in inspect(changeset), Ash.Error.Invalid and validation error messages, telemetry, :sys dumps, and error-tracker payloads. The generated encrypted attribute and decrypt calculation are already hardcoded sensitive. This issue affects ash_cloak: from 0.1.0 before 0.4.0.