Vulnerability advisory
CVE-2026-77970
Sensitive fields nested in embedded values are not redacted in AshPaperTrail versions
Also known as EEF-CVE-2026-77970GHSA-v645-6jm6-cgpj
- CVSS 4.0
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Affected versions
Repository
| Affected commits | Fixed by commit |
|---|---|
| GIT github.com/ash-project/ash_paper_trail ↗ | |
| ffe5e03b14d26b73bff17f3eca811591788aba9c to before 0cd4acfe7f48397673d8594fb5e2cd0f1bda6e40 | 0cd4acfe7f48397673d8594fb5e2cd0f1bda6e40 |
| fd8c9a661b8ec97d592c53207c96b5547e0e811c to before e03925c19365697ceb099d2ceca9ee1f5ce8c8b8 | e03925c19365697ceb099d2ceca9ee1f5ce8c8b8 |
Also listed as affected (10)
| |
Description
Cleartext Storage of Sensitive Information vulnerability in ash-project ash_paper_trail allows an attacker with read access to the generated version resource to recover sensitive values nested inside embedded resources, unions, or lists.
sensitive_attributes :redact and :ignore only act on the tracked resource's top-level attributes. maybe_redact_changes/3 and the stored-action-input path in AshPaperTrail.Resource.Changes.CreateNewVersion derive the sensitive set from the resource's own attributes and never descend into embedded, union, or list values, so a non-sensitive attribute or action argument that holds an embed with a sensitive? field (for example an accepted credentials embed carrying a token) is written to the version table in cleartext.
This issue affects ash_paper_trail: from 0.3.0 before 0.7.0.
References
- Webcna.erlef.org/cves/CVE-2026-77970.html ↗
- Webgithub.com ↗
- Webosv.dev/vulnerability/EEF-CVE-2026-77970 ↗
- Webrepo.hex.pm ↗
- Advisorygithub.com/CVEProject/cvelistV5/tree/main/cves/2026/77xxx/CVE-2026-77970.json ↗
- Advisorygithub.com/ash-project/ash_paper_trail/security/advisories/GHSA-v645-6jm6-cgpj ↗
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-77970 ↗
- Fixgithub.com/ash-project/ash_paper_trail/commit/0cd4acfe7f48397673d8594fb5e2cd0f1bda6e40 ↗
- Packagegithub.com/ash-project/ash_paper_trail ↗