Skip to main content
Menu
CVEs

CVE

mail-parser path traversal in attachment extraction

CVE-2026-129296

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

6.5MediumCNA
Exploited
No known exploitation
Fix
Fixed in 4.6.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 4.6.0.

Published
Last modified
Reference
Last checked
14/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

SpamScope's mail-parser, a Python tool for parsing emails, has a path traversal flaw in its attachment extraction. A remote attacker who sends a crafted email without logging in can write attachments outside the intended output directory and overwrite files the parsing process can access, though this requires a user action.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. From 3.8.0 until 4.6.0, the write_attachments() and write_sample() APIs use attacker-controlled attachment filenames without sufficient sanitization and path containment validation. Directory traversal sequences and absolute filesystem paths can cause an attachment to be written outside the intended output directory. An attacker can overwrite files accessible to the parsing process when an application extracts attachments from a crafted message. This issue is fixed in version 4.6.0.

cve.now Index

14Pcve.now Index 14 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.5/10CVSS 6.5
  • No patch0/5No signal

What would change the score

  • Would score about 69 if added to CISA KEV
  • Would score about 64 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 4.6.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129296 (mail-parser: Path Traversal vulnerability in attachment extraction), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129296 (entry last updated 2026-11-16):
Affected:
- SpamScope mail-parser: from 3.8.0, fixed in 4.6.0
Fixed versions: 4.6.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129296 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129296 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/SpamScope/mail-parser/security/advisories/GHSA-fr3h-cpq2-9496
- https://github.com/SpamScope/mail-parser/pull/165
- https://github.com/SpamScope/mail-parser/commit/3d6cb7a51f2ad7ea57e529121dbd5d56f29fefe8
- https://github.com/SpamScope/mail-parser/commit/b0a2e968815f3ed9e129efb0f5f7e935a9dacd1d
- https://github.com/SpamScope/mail-parser/releases/tag/4.6.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129296
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129296"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • SpamScope mail-parser

    From 3.8.0 · fixed in 4.6.0

Evidence 7

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 4

  1. Repository
  2. Repository
  3. Repository
  4. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129296

Is CVE-2026-129296 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-129296?

mail-parser: from 3.8.0 before 4.6.0.Source: cve.now feed data

How do I fix CVE-2026-129296?

Upgrade to a fixed version: 4.6.0.Source: cve.now feed data