CVE-2026-129297: mail-parser · Sender IP address spoofing in get_server_ipaddress()
Affects parsedmarcSource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 10.4.2 soon.
Data as of 17 Nov 2026, 18:06 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.5 |
|---|
- Patch
- Available – fixed in 10.4.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NExploitation 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.4.2.
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.2 or later, where the vulnerability is fixed. If upgrading is not possible, do not trust the return value of get_server_ipaddress() for sender IP attribution. Instead, rely on authenticated signals such as MTA logs or SPF/DKIM/DMARC verification results computed outside the library. There are no internal workarounds within mail-parser.
Description
A vulnerability in mail-parser's get_server_ipaddress() function allowed sender IP address spoofing due to unreliable candidate address selection. This was fixed in version 4.6.2 by changing how candidate addresses are selected and improving IPv6 pattern matching. The function now returns None in cases where it previously returned unreliable addresses, requiring callers to handle this new behavior. No workarounds exist within mail-parser itself; callers unable to upgrade should rely on authenticated signals like MTA logs or SPF/DKIM/DMARC results for sender attribution.
References
- github.com/SpamScope/mail-parser/security/advisories/GHSA-72px-j8gh-p79x (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-129297 (opens in a new tab)
- github.com/SpamScope/mail-parser/pull/167 (opens in a new tab)
- github.com/SpamScope/mail-parser/commit/ce3cf3559db1ff806bda598b378de9f8c2a5be96 (opens in a new tab)
- github.com/SpamScope/mail-parser (opens in a new tab)
- github.com/SpamScope/mail-parser/releases/tag/4.6.2 (opens in a new tab)