CVE-2026-77970

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: CVSS: 5.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.9
EG Score
5.9(low)
EG Risk
31(Track)
EG Risk 31/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity59% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
EPSS %ILE
KEV
Not listed

Published

August 30, 2026

Last Modified

August 30, 2026

Advisory Details (4)

Auto-updated Aug 30, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit

commit 0cd4acfe7f48 (ash-project/ash_paper_trail)

Fix landed in ash-project/ash_paper_trail commit 0cd4acfe7f48 — awaiting tagged release

https://github.com/ash-project/ash_paper_trail/commit/0cd4acfe7f48397673d8594fb5e2cd0f1bda6e40
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-77970
github Patch Available🟡 PoC Available

Sensitive information exposure in AshPaperTrail stores nested sensitive values in plaintext in the version table · Advisory · ash-project/ash_paper_trail · GitHub

https://github.com/ash-project/ash_paper_trail/security/advisories/GHSA-v645-6jm6-cgpj

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 3× in last 7d / 3× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:29 UTCEG score recompute
  2. 2026-08-30 00:25 UTCEG score recompute
  3. 2026-08-30 00:22 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-77970?
CVE-2026-77970 is a medium vulnerability published on August 30, 2026. Cleartext Storage of Sensitive Information vulnerability in ash-project ashpapertrail allows an attacker with read access to the generated version resource to recover sensitive values nested inside embedded resources, unions, or lists. sensitiveattributes :redact and :ignore only act on the tracked…
When was CVE-2026-77970 disclosed?
CVE-2026-77970 was first published in the National Vulnerability Database on August 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-77970?
CVE-2026-77970 has a CVSS v3 base score of 5.9 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-77970?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-77970, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-77970

Explore →

Is Your Infrastructure Affected by CVE-2026-77970?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.