CVE-2026-81322: Cloaked plaintext leaks through a non-sensitive action argument in AshCloak

Severity: low (CVSS 2.1 v4.0)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.1% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-08-30 · updated 2026-09-01
Weakness: CWE-200

Description

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.

Affected products

ash-project ash_cloak: from 0.1.0 before 0.4.0 — fixed in 0.4.0

How to fix

Upgrade to a fixed version: ash-project ash_cloak 0.4.0. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-81322 or the next vulnerability affects your stack