CVE-2026-129301

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.5 from GitHub Security Advisory (severity: MODERATE) published 2026-11-16. A secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-126575 (ENISA EUVD) · GHSA-8cgq-x343-p74c (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. From 4.6.0 until 4.6.3, write_attachments() calls _safe_attachment_filename() and write_sample() without isolating failures for individual attacker-controlled MIME parts. An RFC 2231 filename containing a NUL, a basename exceeding NAME_MAX, or an undecodable base64 payload can raise ValueError, OSError, or binascii.Error and abort the entire save loop. Later attachments remain unwritten; when a caller catches only MailParserError, the failure is not surfaced through the expected library-exception path. If a downstream scanner or sandbox reads only the extraction directory, a payload after the crafted part can be missed even though it remains in the delivered message, and the aborted batch also causes availability loss. This issue is fixed in version 4.6.3.

CVSS v3
6.5
EG Score
6.5MEDIUMhigh confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
27th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 16, 2026

Last Modified

November 18, 2026

Advisory Details (5)

Auto-updated Nov 16, 2026
Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub release Patch Available

4.6.3

Patch available: SpamScope/mail-parser 4.6.3

https://github.com/SpamScope/mail-parser/releases/tag/4.6.3
GitHub commit Patch Available

commit e1d9fe677804 (SpamScope/mail-parser)

Patch available: SpamScope/mail-parser 4.6.3 (contains commit e1d9fe677804)

https://github.com/SpamScope/mail-parser/commit/e1d9fe6778045d6e2c44406bc8822e3464c1097f
GitHub commit

commit 11b894a0b8b3 (SpamScope/mail-parser)

Fix landed in SpamScope/mail-parser commit 11b894a0b8b3 — awaiting tagged release

https://github.com/SpamScope/mail-parser/commit/11b894a0b8b3f11055a99caff118206138d1daba
GitHub pull request Patch Available

fix: attachment integrity, batch availability, and date overflow on hostile mail

Patch available: SpamScope/mail-parser 4.6.3 (PR #171 merged 2026-08-19)

https://github.com/SpamScope/mail-parser/pull/171
GitHub advisoryMentions a patch (unverified)

One hostile attachment aborts `write_attachments()` and silently drops the rest of the batch · Advisory · SpamScope/mail-parser · GitHub

https://github.com/SpamScope/mail-parser/security/advisories/GHSA-8cgq-x343-p74c

Vendor Advisories for CVE-2026-129301(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipmail-parser @ 4.6.3 (fixes >= 4.6.0, < 4.6.3)—ghsa

These rows come from GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
mail-parser4.6.0, 4.6.1, 4.6.2
  • 4.6.0 up to 4.6.3: fixed in 4.6.3
—

Weakness Classification(2)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  3. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  4. 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  5. 2026-11-18 16:28 UTCEchelonGraph re-scored
  6. 2026-11-18 16:28 UTCGHSA enrichmentGHSA-8cgq-x343-p74c · GitHub severity MODERATE · GitHub CVSS 6.5
  7. 2026-11-18 15:23 UTCEchelonGraph re-scored
  8. 2026-11-18 15:23 UTCGHSA enrichmentGHSA-8cgq-x343-p74c · GitHub severity MODERATE · GitHub CVSS 6.5
  9. 2026-11-17 18:53 UTCEchelonGraph re-scored
  10. 2026-11-17 18:53 UTCGHSA enrichmentGHSA-8cgq-x343-p74c · GitHub severity MODERATE · GitHub CVSS 6.5
  11. 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  12. 2026-11-16 19:03 UTCENISA EUVD ID recordedEUVD-2026-126575 · Source: ENISA EUVD
  13. 2026-11-16 18:29 UTCEchelonGraph re-scored
  14. 2026-11-16 17:50 UTCEchelonGraph re-scoredFirst assessed: 6.5 MEDIUM
  15. 2026-11-16 17:48 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-129301?
CVE-2026-129301 is a medium-severity vulnerability; its CVE record was published on November 16, 2026. mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. From 4.6.0 until 4.6.3, write_attachments() calls _safe_attachment_filename() and write_sample() without isolating failures for individual…
When was the CVE record for CVE-2026-129301 published?
The CVE record for CVE-2026-129301 was published on November 16, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 18, 2026; the record at its source may have been updated since.
Is CVE-2026-129301 actively exploited?
CVE-2026-129301 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-129301?
CVE-2026-129301 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-129301?
A fix for CVE-2026-129301 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-129301 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-129301

Explore →

Is Your Infrastructure Affected by CVE-2026-129301?

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