Skip to main content
Menu
CVEs

CVE

mail-parser uncaught exception in write_attachments() drops attachments

CVE-2026-129301

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

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

Do first: Upgrade to a fixed version: 4.6.3.

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

Summary

mail-parser from SpamScope has a flaw in `write_attachments()` where one hostile email attachment stops the save loop, leaving later attachments unwritten. An attacker can trigger this remotely by sending an email, without logging in or any user action, and can hide later payloads from scanners that read only the extraction directory while causing a loss of availability.

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

cve.now Index

24Pcve.now Index 24 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable 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.3.

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-129301 (mail-parser: One hostile attachment aborts `write_attachments()` and silently drops the rest of the batch), 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-129301 (entry last updated 2026-11-16):
Affected:
- SpamScope mail-parser: from 4.6.0, fixed in 4.6.3
Fixed versions: 4.6.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129301 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129301 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-8cgq-x343-p74c
- https://github.com/SpamScope/mail-parser/pull/171
- https://github.com/SpamScope/mail-parser/commit/11b894a0b8b3f11055a99caff118206138d1daba
- https://github.com/SpamScope/mail-parser/commit/e1d9fe6778045d6e2c44406bc8822e3464c1097f
- https://github.com/SpamScope/mail-parser/releases/tag/4.6.3
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-129301
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-129301"}.

Timeline

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

Affected versions

  • SpamScope mail-parser

    From 4.6.0 · fixed in 4.6.3

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-129301

Is CVE-2026-129301 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-129301?

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

How do I fix CVE-2026-129301?

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