CVE-2026-129295

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-11-16. A secondary CVSS source baseline 7.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-126570 (ENISA EUVD) · GHSA-r7w7-vpq8-c5vv (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.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.2.0 until 4.6.1, attacker-controlled email headers can cause polynomial regular-expression backtracking during ordinary parse_from_string(), parse_from_bytes(), or parse_from_file() calls. In src/mailparser/utils.py, get_addresses() invokes the _ADDR_FALLBACK_RE fallback when strict address parsing yields no usable address, and overlapping quantifiers rescan padded address headers quadratically or cubically. In src/mailparser/const.py, parse_received() applies _CLAUSE_SPLITTER to uncollapsed whitespace in a Received header, causing quadratic backtracking when a whitespace run is not followed by a clause keyword. A small, well-formed message can keep mail gateway, ticketing, quarantine, or archival parsing workers busy for extended periods. This issue is fixed in version 4.6.1.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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.5%
EPSS %ILE
43rd
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% 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 17, 2026

Advisory Details (6)

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

4.6.1

Patch available: SpamScope/mail-parser 4.6.1

https://github.com/SpamScope/mail-parser/releases/tag/4.6.1
GitHub commit

commit 85e53f820d78 (SpamScope/mail-parser)

Fix landed in SpamScope/mail-parser commit 85e53f820d78 — awaiting tagged release

https://github.com/SpamScope/mail-parser/commit/85e53f820d78ae7c955dafbbcd0e20989a735c2c
GitHub commit Patch Available

commit 5aab122f0d76 (SpamScope/mail-parser)

Patch available: SpamScope/mail-parser 4.6.1 (contains commit 5aab122f0d76)

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

commit 037293158cb2 (SpamScope/mail-parser)

Fix landed in SpamScope/mail-parser commit 037293158cb2 — awaiting tagged release

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

Security hardening: ReDoS, recursion DoS, and Outlook-path robustness

Patch available: SpamScope/mail-parser 4.6.1 (PR #166 merged 2026-08-12)

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

mail-parser is vulnerable to polynomial ReDoS in email header parsing · Advisory · SpamScope/mail-parser · GitHub

https://github.com/SpamScope/mail-parser/security/advisories/GHSA-r7w7-vpq8-c5vv

Vendor Advisories for CVE-2026-129295(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.1 (fixes >= 4.2.0, < 4.6.1)—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.2.0 ... 4.6.0 (6 versions)
  • 4.2.0 up to 4.6.1: fixed in 4.6.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 11× 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.5% · 43rd percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  3. 2026-11-19 20:26 UTCOSV refresh
  4. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  5. 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  6. 2026-11-17 23:28 UTCEchelonGraph re-scored
  7. 2026-11-17 23:28 UTCGHSA enrichmentGHSA-r7w7-vpq8-c5vv · GitHub severity HIGH · GitHub CVSS 7.5
  8. 2026-11-17 22:33 UTCEchelonGraph re-scored
  9. 2026-11-17 22:33 UTCGHSA enrichmentGHSA-r7w7-vpq8-c5vv · GitHub severity HIGH · GitHub CVSS 7.5
  10. 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  11. 2026-11-17 11:12 UTCEchelonGraph re-scored
  12. 2026-11-17 11:12 UTCGHSA enrichmentGHSA-r7w7-vpq8-c5vv · GitHub severity HIGH · GitHub CVSS 7.5
  13. 2026-11-16 19:03 UTCENISA EUVD ID recordedEUVD-2026-126570 · Source: ENISA EUVD
  14. 2026-11-16 18:29 UTCEchelonGraph re-scored
  15. 2026-11-16 17:41 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
  16. 2026-11-16 17:38 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-129295?
CVE-2026-129295 is a high-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.2.0 until 4.6.1, attacker-controlled email headers can cause polynomial regular-expression backtracking during ordinary parse_from_string(),…
When was the CVE record for CVE-2026-129295 published?
The CVE record for CVE-2026-129295 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 17, 2026; the record at its source may have been updated since.
Is CVE-2026-129295 actively exploited?
CVE-2026-129295 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-129295?
CVE-2026-129295 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-129295?
A fix for CVE-2026-129295 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-129295 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-129295

Explore →

Is Your Infrastructure Affected by CVE-2026-129295?

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