CVE
mail-parser sender IP spoofing in get_server_ipaddress()
mail-parser 4.6.1 and earlier can return an attacker-chosen sender IP from get_server_ipaddress(). Fixed in 4.6.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- Exploited
- No known exploitation
- Fix
- Fixed in 4.6.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.6.2.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 28/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
Mail-parser, a Python tool for parsing emails, can be tricked into reporting a forged sender IP address. Its get_server_ipaddress() function can pick an address that the attacker wrote into the message's Received headers, and this can be done remotely by sending a crafted email without logging in.
Original description
mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. Prior to 4.6.2, get_server_ipaddress() can select an attacker-controlled address from attacker-controlled Received headers. The minimum mechanism needed to distinguish this spoofing issue, derived from the advisory's remediation analysis and verified fix evidence, is appearance-based candidate selection that can treat bracketed IPv4 or IPv6 addresses or HELO markers in sender-written text as MTA-recorded addresses and can continue past a trusted hop that names no address. Applications that rely on the returned value can attribute a message to an attacker-selected sender IP address. This issue is fixed in version 4.6.2.
Who should check
Teams running SpamScope mail-parser 4.6.1 or earlier that call get_server_ipaddress() and use its result to attribute messages to a sender IP.
“Fixed in 4.6.2 . Upgrade with pip install --upgrade mail-parser .”
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 4.6.2.
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-129297 (mail-parser: Sender IP address spoofing in `get_server_ipaddress()), 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-129297 (entry last updated 2026-11-16):
Affected:
- SpamScope mail-parser: fixed in 4.6.2
Fixed versions: 4.6.2.
Conditions (all must be true for the bug to be hit):
- mail-parser version 4.6.1 or earlier (source: https://github.com/SpamScope/mail-parser/security/advisories/GHSA-72px-j8gh-p79x)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129297 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129297 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-72px-j8gh-p79x
- https://github.com/SpamScope/mail-parser/pull/167
- https://github.com/SpamScope/mail-parser/commit/ce3cf3559db1ff806bda598b378de9f8c2a5be96
- https://github.com/SpamScope/mail-parser/releases/tag/4.6.2
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-129297
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-129297"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- SpamScope mail-parser
fixed in 4.6.2
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 3
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129297
Is CVE-2026-129297 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
What does this mean?
get_server_ipaddress() can return a sender IP address that an attacker chose instead of the real one. That value is used for attribution and blocklisting, so those decisions lose integrity.Source: github.com, github.com
Which versions are affected by CVE-2026-129297?
mail-parser: before 4.6.2.Source: cve.now feed data
Am I affected, and how do I check?
Versions of mail-parser 4.6.1 or earlier are affected. To check the installed version, run pip show mail-parser.Source: github.com, github.com
How do I fix CVE-2026-129297?
Upgrade to mail-parser 4.6.2 with pip install --upgrade mail-parser.Source: github.com, github.com