CVE-2026-81322: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in ash-project ash_cloak
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.
CVSS v4.0
Score 2.1low
Affected software
ash-project
ash_cloak
ash-project
ash_cloak
cpe:2.3:a:ash-project:ash_cloak:*:*:*:*:*:*:*:*Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in ash_cloak occurs because AshCloak.Transformers.SetUpEncryption removes cloaked attributes from the action's accept list and adds a plaintext argument carrying the sensitive data. If a cloaked attribute is declared without the sensitive? flag set to true, the plaintext value is treated as non-sensitive and is not redacted. Consequently, this plaintext appears in inspect(changeset), validation error messages, telemetry, system dumps, and error-tracker payloads, exposing sensitive information. The encrypted attribute and decryption calculations are correctly marked sensitive, but the plaintext argument is not, leading to this exposure.
Potential Impact
Sensitive plaintext data that should be encrypted can be exposed to anyone with access to logs, error trackers, crash reports, or who can trigger validation errors. This could lead to unauthorized disclosure of sensitive information. However, the impact is limited by the requirement of local access to logs or the ability to trigger validation errors, and the CVSS score is low.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should avoid declaring cloaked attributes without the sensitive? flag set to true to prevent plaintext exposure. Monitor vendor communications for updates and patches.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- EEF
- Date Reserved
- 2026-08-30T06:00:01.266Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a947173acd9273b49d99f4e
Added to database: 08/30/2026, 18:07:47 UTC
Last enriched: 09/07/2026, 15:07:41 UTC
Last updated: 10/13/2026, 06:48:19 UTC
Views: 89
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.