Skip to main content
VulnerabilityPublished

CVE-2026-129296: mail-parser · Path Traversal vulnerability in attachment extraction

Affects mail-parserSource GCVE Database

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

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

Data as of 16 Nov 2026, 23:12 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.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

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.0.

Affected software

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

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

AI-suggested

A patch is available in mail-parser version 4.6.0 that addresses this vulnerability. Users should upgrade to version 4.6.0 or later to ensure comprehensive filename sanitization and path validation are applied. No additional mitigations are necessary if the patched version is used.

Description

mail-parser versions 3.8.0 through 4.5.0 contain a path traversal vulnerability in the write_attachments() and write_sample() APIs. Maliciously crafted email attachments with filenames containing directory traversal sequences or absolute paths could cause files to be written outside the intended directory, potentially leading to arbitrary file overwrite. The issue is fixed in version 4.6.0 by sanitizing filenames, validating output paths, rejecting symbolic links, and normalizing path separators.

References

Community reviews

Loading reviews…