CVE-2026-82521

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 66% of all CVEs by exploit prediction. 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: epss, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

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

parsedmarc 9.0.6 before 11.0.1 writes forensic report sample files using an output path derived from the email subject. When the subject consists entirely of path traversal sequences, the filename sanitization function produces an empty string, and a fallback to the raw unsanitized subject causes the resulting file to be written outside the intended samples directory. An attacker who can cause a forensic failure report with a crafted Subject to be processed can write a dot-prefixed file with attacker-controlled content to an ancestor directory of the configured samples output path. Exploitation requires that file output for forensic report samples is enabled.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/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
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

Published

September 3, 2026

Last Modified

September 24, 2026

Advisory Details (3)

Auto-updated Sep 3, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github.
generic

parsedmarc 9.0.6 < 11.0.1 Path Traversal via Forensic Report Subject | Advisories | VulnCheck

https://www.vulncheck.com/advisories/parsedmarc-path-traversal-via-forensic-report-subject
github_release Patch Available

11.0.1

Patch available: domainaware/parsedmarc 11.0.1

https://github.com/domainaware/parsedmarc/releases/tag/11.0.1
github Patch Available🟡 PoC Available

Path Traversal via Email Subject in Forensic Sample Output · Advisory · domainaware/parsedmarc · GitHub

https://github.com/domainaware/parsedmarc/security/advisories/GHSA-c284-w5m6-jhjm

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 40× 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-09-24 21:13 UTCEG score recompute
  2. 2026-09-24 14:04 UTCEPSS rescore
  3. 2026-09-24 06:18 UTCEG score recompute
  4. 2026-09-23 17:54 UTCEPSS rescore
  5. 2026-09-23 07:09 UTCEG score recompute
  6. 2026-09-22 16:01 UTCEPSS rescore
  7. 2026-09-22 08:01 UTCEG score recompute
  8. 2026-09-21 21:09 UTCEPSS rescore
  9. 2026-09-21 08:51 UTCEG score recompute
  10. 2026-09-20 20:16 UTCEPSS rescore
  11. 2026-09-20 09:27 UTCEG score recompute
  12. 2026-09-19 10:17 UTCEG score recompute
  13. 2026-09-18 19:28 UTCEPSS rescore
  14. 2026-09-18 11:08 UTCEG score recompute
  15. 2026-09-17 11:59 UTCEG score recompute
  16. 2026-09-16 14:08 UTCEPSS rescore
  17. 2026-09-16 12:50 UTCEG score recompute
  18. 2026-09-16 05:15 UTCEPSS rescore
  19. 2026-09-15 13:41 UTCEG score recompute
  20. 2026-09-15 03:12 UTCEPSS rescore
  21. 2026-09-15 03:12 UTCEPSS rescore
  22. 2026-09-14 14:32 UTCEG score recompute
  23. 2026-09-14 14:00 UTCEG score recompute
  24. 2026-09-13 20:03 UTCEG score recompute
  25. 2026-09-12 20:54 UTCEG score recompute
Show 15 more
  1. 2026-09-11 21:45 UTCEG score recompute
  2. 2026-09-11 14:53 UTCEPSS rescore
  3. 2026-09-11 14:53 UTCEPSS rescore
  4. 2026-09-10 22:36 UTCEG score recompute
  5. 2026-09-08 23:06 UTCEG score recompute
  6. 2026-09-08 22:01 UTCEPSS rescore
  7. 2026-09-07 17:58 UTCEG score recompute
  8. 2026-09-06 18:49 UTCEG score recompute
  9. 2026-09-06 13:48 UTCEPSS rescore
  10. 2026-09-05 19:39 UTCEG score recompute
  11. 2026-09-05 15:31 UTCEPSS rescore
  12. 2026-09-04 20:30 UTCEG score recompute
  13. 2026-09-03 21:21 UTCEG score recompute
  14. 2026-09-03 20:51 UTCEG score recompute
  15. 2026-09-03 20:48 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82521?
CVE-2026-82521 is a medium vulnerability published on September 3, 2026. parsedmarc 9.0.6 before 11.0.1 writes forensic report sample files using an output path derived from the email subject. When the subject consists entirely of path traversal sequences, the filename sanitization function produces an empty string, and a fallback to the raw unsanitized subject causes…
When was CVE-2026-82521 disclosed?
CVE-2026-82521 was first published in the National Vulnerability Database on September 3, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82521 actively exploited?
CVE-2026-82521 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 65.6% of all scored CVEs.
What is the CVSS score of CVE-2026-82521?
CVE-2026-82521 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-82521?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82521, 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-82521

Explore →

Is Your Infrastructure Affected by CVE-2026-82521?

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

Book a Demo →Browse All CVEs