Sensitive-data disclosure via shallow audit-log redaction
Published Aug 30, 2026 · Updated Aug 30, 2026
Cleartext storage in Ash Framework AshPaperTrail 0.3.0 through 0.6.0 allows attackers to recover nested secrets via reads of generated version resources. maybe_redact_changes/3 and the stored-action-input path derive a flat sensitive-field set from only top-level resource attributes, then persist embedded, union, map, or list values without recursively redacting sensitive fields. Exposure requires :redact or :ignore mode, a nested sensitive field inside a versioned attribute or accepted action input, and read access to the generated version resource.
Summary
What happened
Cleartext storage in Ash Framework AshPaperTrail 0.3.0 through 0.6.0 allows attackers to recover nested secrets via reads of generated version resources. maybe_redact_changes/3 and the stored-action-input path derive a flat sensitive-field set from only top-level resource attributes, then persist embedded, union, map, or list values without recursively redacting sensitive fields. Exposure requires :redact or :ignore mode, a nested sensitive field inside a versioned attribute or accepted action input, and read access to the generated version resource.
The record
- CVE
- CVE-2026-77970
- Published
- Aug 30, 2026
- Updated
- Aug 30, 2026
- Vendor
- Ash Framework
- Product
- AshPaperTrail
- Classifications
- CWE-312, CAPEC-37, T1005
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 30, 2026CVE publishedPublication date reported by the CVE source.
- Aug 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.3.0 <0.7.0
- Affected versionversion=ffe5e03b14d26b73bff17f3eca811591788aba9c <0cd4acfe7f48397673d8594fb5e2cd0f1bda6e40
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Embedded-value redaction proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo