parsedmarc · mail-parser: One hostile attachment aborts `write_attachments()` and silently drops the rest of the batch
Affects parsedmarcSource GCVE Database
Not known to be exploited · CVSS 6.5 Medium : upgrade to 10.5.0 when convenient.
Data as of 17 Nov 2026, 18:06 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 6.5 |
|---|
- Patch
- Available – fixed in 10.5.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.5.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewparsedmarcpkg:brew/parsedmarcOther threats | Affected
| Fixed in
|
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, or parsedmarc to version 10.5.0 or later, where the issue is fixed. The fix includes skipping invalid attachments instead of aborting, truncating long filenames, and improved base64 decoding and error handling. If upgrading is not possible, avoid calling write_attachments() on untrusted mail. Instead, iterate over parser.attachments and write each attachment individually inside try/except blocks, skipping attachments with a None safe_filename.
Description
A vulnerability in mail-parser versions 10.4.2 up to but not including 10.5.0 causes the write_attachments() function to abort writing attachments after encountering a single malicious attachment, silently dropping subsequent attachments without error. This allows an attacker to evade detection by placing a poisoned attachment first, preventing later payloads from being extracted by downstream scanners while still delivering them intact to recipients. The issue arises from unguarded exceptions during filename sanitization and payload decoding. The flaw was fixed in version 10.5.0 by improving error handling, filename truncation, and decoding logic.
References
- github.com/SpamScope/mail-parser/security/advisories/GHSA-8cgq-x343-p74c (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-129301 (opens in a new tab)
- github.com/SpamScope/mail-parser/pull/171 (opens in a new tab)
- github.com/SpamScope/mail-parser/commit/11b894a0b8b3f11055a99caff118206138d1daba (opens in a new tab)
- github.com/SpamScope/mail-parser/commit/e1d9fe6778045d6e2c44406bc8822e3464c1097f (opens in a new tab)
- github.com/SpamScope/mail-parser (opens in a new tab)
- github.com/SpamScope/mail-parser/releases/tag/4.6.3 (opens in a new tab)