Vulnerability EEF-CVE-2026-81322

Unknown
UNKNOWN RISK
Vulnerabilities without an assigned CVSS score. Severity is not determinable from available data.
2 months ago
August 30, 2026 at 06:06 PM UTC
Cloaked plaintext leaks through a non-sensitive action argument in AshCloak
0.1.0 - 0.3.1
0.1.0 - 0.3.1

Summary

Cloaked plaintext leaks through a non-sensitive action argument in AshCloak

Details

Summary

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.

Configurations

A resource must cloak an attribute that is not itself declared sensitive? true, and the plaintext must reach an output that renders it (a create/update validation error returned to the client, or logs, telemetry, or crash reports that capture the changeset or error).

Impacted packages

Timeline

Published
2 months ago
August 30, 2026 at 06:06 PM UTC
Fixed (0.4.0)
2 months ago
August 30, 2026 at 03:45 PM UTC
Last Modified
1 day ago
November 20, 2026 at 05:23 PM UTC