Skip to main content
No exploitation reportedFix availableAwaiting NVD analysis

CVE-2026-129301

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

No exploitation reported by the sources we read.

  • Published2026-11-16
  • Fixed in4.6.3
  • WeaknessCWE-248 · CWE-436

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2026-11-1617:47CVE publishedCNA

Versions per branch

OSV
mail-parser
BranchAffectedFixed in
4.6≥ 4.6.0, < 4.6.34.6.3

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • SpamScope mail-parser
    Affected
    • = >= 4.6.0, < 4.6.3no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-16

Fix

  1. Update mail-parser to 4.6.3

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Metasploit modules
none listed
Metasploit Framework

Sources

  • CNACVSS 3.16.52026-11-16
  • CNAweakness (CWE)CWE-248, CWE-4362026-11-16
  • NVDweakness (CWE)CWE-248, CWE-436read 2026-11-16
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryMODERATE2026-11-16

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
Published
2026-11-16
Last Modified
2026-11-16
NVD status
Received
GitHub Advisory
GHSA-8cgq-x343-p74c

Frequently asked questions

What is CVE-2026-129301?

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.

Is CVE-2026-129301 actively exploited?

Active exploitation of CVE-2026-129301 has not been confirmed.

What is the CVSS score for CVE-2026-129301?

CVE-2026-129301 has a CVSS v3 base score of 6.5 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L.

Running mail-parser? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record