# CVE-2026-129297: mail-parser: Sender IP address spoofing in `get_server_ipaddress()

> Attackers can spoof sender IP addresses in Received headers so mail-parser attributes messages to attacker-controlled hosts; apps relying on it should care.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** Yes (`get_server_ipaddress()`)
- **Fix available:** Yes
- **Published:** 16 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-72px-j8gh-p79x

## What is CVE-2026-129297?

CVE-2026-129297 is a high-severity security feature bypass vulnerability in SpamScope mail-parser, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-129297?

1 open source package ship an affected version, including mail-parser.

An affected version is only exploitable if your software calls get_server_ipaddress(). Many projects that include it are not exposed.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `mail-parser` | PyPI | `pkg:pypi/mail-parser` | All versions | 4.6.2 |

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| Upstream |  | fixed | `mail-parser` | 4.6.2 |

## How do I fix CVE-2026-129297?

Upgrade mail-parser to 4.6.2 or later.

## Is CVE-2026-129297 being exploited?

There is no known exploitation of CVE-2026-129297 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129297 and fix it if it is affected.

What it is: CVE-2026-129297 is a high-severity security feature bypass vulnerability in SpamScope mail-parser, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-129297 in the wild and no public exploit code.
Exposure: An affected version is only exploitable if your software calls get_server_ipaddress(). Many projects that include it are not exposed.

Affected packages and fixed versions:
- mail-parser (PyPI): affected all versions; fixed in 4.6.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
   If an affected version is present, also search the code for calls to get_server_ipaddress() and report whether any exist.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-129297/ (Markdown: https://insights.sbomify.com/CVE-2026-129297/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-129297
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-129297
- OSV: https://osv.dev/vulnerability/CVE-2026-129297

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-129297/
Summaries are generated and may contain mistakes; the official description above is the record.
