cve.bz

CVE-2026-129301 mail-parser: One hostile attachment aborts `write_attachments()` and silently drops the rest of the batch

6.5 mediumEPSS 0.3%Fix available

Medium (6.5) in spamscope mail-parser. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in mail-parser 4.6.3.

On this page
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.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 27th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-248 Uncaught Exception
CWE-436 Interpretation Conflict
OWASP Top 10
A06:2025 Insecure Design, A10:2025 Mishandling of Exceptional Conditions
Published
Assigned by
GitHub_M (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • mail-parser (PyPI): fixed in 4.6.3

Ask an AI about this CVE

Show the promptExplain CVE-2026-129301 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-129301?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-129301?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-129301 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
SpamScope mail-parser>= 4.6.0, < 4.6.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-8cgq-x343-p74cPyPImail-parser>=4.6.0 <4.6.34.6.3

Attack patterns (CAPEC)

  • CAPEC-34 HTTP Response Splitting Likelihood: Medium · Severity: High
  • CAPEC-105 HTTP Request Splitting Likelihood: Medium · Severity: High
  • CAPEC-273 HTTP Response Smuggling Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON