Skip to main content
VulnerabilityPublished

CVE-2026-129299: SpamScope mail-parser · Uncaught Exception

Affects SpamScope mail-parserSource CVE Database V5

0
Compare

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

Data as of 16 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 4.6.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 15 Nov 2026.

What to do

Upgrade SpamScope mail-parser to 4.6.2.

Affected software

ProductAffectedFixed in
SpamScopemail-parserAffected
  • <4.6.2
Fixed in
  • 4.6.2

AI-suggested

Upgrade mail-parser to version 4.6.2 or later, where these issues have been fixed. No other mitigation is indicated or required.

Description

mail-parser versions prior to 4.6.2 have multiple issues where exceptions can be raised or content can be silently lost during email message processing. These include TypeErrors caused by header collisions with method names and improper handling of 8-bit header values during JSON serialization. Additionally, some headers may be substituted or disappear without error, and headerless messages can cause empty body and attachment outputs without signaling errors. These flaws can interrupt message processing or conceal malicious indicators from downstream scanners. The issues are fixed in version 4.6.2.

References

Community reviews

Loading reviews…