Skip to main content
VulnerabilityPublished

CVE-2026-129299: Uncaught exceptions and silent header loss in mail-parser on attacker-controlled input

Affects parsedmarcSource GCVE Database

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

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

Data as of 17 Nov 2026, 18:06 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 10.4.2
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 parsedmarc to 10.4.2.

Affected software

ProductAffectedFixed in
Homebrewparsedmarcpkg:brew/parsedmarcOther threatsAffected
  • >=8.11.0 <10.4.2
Fixed in
  • 10.4.2

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.2 or later, where these issues are fixed. If upgrading is not immediately possible, callers should wrap accesses to mail_json, mail_partial_json, headers_json, and any _raw header access in a broad exception handler to catch exceptions beyond mail-parser's own error classes. There are no workarounds for the silent data loss issue other than upgrading.

Description

The mail-parser library versions prior to 4.6.2 contain multiple issues related to handling of email headers from attacker-controlled input. These include uncaught exceptions caused by header names colliding with method names, silent loss or substitution of header values due to normalization and attribute lookup, and improper handling of 8-bit byte headers leading to serialization errors. These flaws can cause worker crashes or evasion of content detection without signaling defects. The issues were fixed in version 4.6.2 by changing header lookup to literal keys, proper initialization, and safer serialization.

References

Community reviews

Loading reviews…