Skip to main content
CVE-2026-129301VulnerabilityPublished

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

Affects mail-parserSource GCVE Database

0
Compare
Authoritative record:CVE-2026-129301· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 4.6.3 when convenient.

Data as of 17 Nov 2026, 00:04 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.16.5
Patch
Available – fixed in 4.6.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade mail-parser to 4.6.3.

Affected software

ProductAffectedFixed in
PyPImail-parserAffected
  • >=4.6.0 <4.6.3
Fixed in
  • 4.6.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade mail-parser to version 4.6.3 or later, where this issue is fixed. If upgrading is not possible, avoid calling write_attachments() on untrusted mail. Instead, iterate over parser.attachments and write each attachment individually within a try/except block, skipping attachments with a None safe_filename. This manual handling prevents a single malicious attachment from aborting the entire batch extraction.

Description

A vulnerability in mail-parser versions 4.6.0 through 4.6.2 causes the write_attachments() function to abort and silently drop all subsequent attachments when encountering a single malicious attachment with crafted MIME metadata. This results in an evasion technique where a malicious attachment placed first prevents later payloads from being saved to disk, although they still reach the recipient's mail client intact. The issue is fixed in version 4.6.3, which improves filename validation, truncates overlong names, and moves base64 decoding before file creation to prevent zero-byte stubs. Users are advised to upgrade to 4.6.3 or implement manual attachment handling with error catching for untrusted mail.

References

Community reviews

Loading reviews…