CVE-2026-129297
validatedZero produced an exploit or a check.GHSA-72px-j8gh-p79x ↗EUVD-2026-126572 ↗
description
SpamScope mail-parser versions before 4.6.2 can select an attacker-controlled IP address while processing Received headers. An attacker may cause applications that trust get_server_ipaddress() to attribute a message to a chosen sender IP address; this requires the application to rely on that returned value for attribution.
mitigation
Upgrade mail-parser to version 4.6.2 or later. Until upgraded, do not use get_server_ipaddress() output as the sole basis for sender-IP attribution or security decisions.
fixed in 4.6.2
outcome
Contextual check: a technique exists and was validated, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-11-16 17:39Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-129297
{ "etk_id": "ETK-2026-4605", "cve_id": "CVE-2026-129297", "display_id": "CVE-2026-129297", "ghsa_id": "GHSA-72px-j8gh-p79x", "euvd_id": "EUVD-2026-126572", "status": "published", "anchor_state": "anchored", "title": "Spoofed sender IP attribution in SpamScope mail-parser", "summary": "SpamScope mail-parser versions before 4.6.2 can select an attacker-controlled IP address while processing Received headers. An attacker may cause applications that trust get_server_ipaddress() to attribute a message to a chosen sender IP address; this requires the application to rely on that returned value for attribution.", "mitigation": "Upgrade mail-parser to version 4.6.2 or later. Until upgraded, do not use get_server_ipaddress() output as the sole basis for sender-IP attribution or security decisions.", "vendor": "SpamScope", "product": "mail-parser", "affected": [ { "affected_notes": [], "affected_ranges": [ "<= 4.6.1" ], "ecosystem": "pip", "fixed_versions": [ "4.6.2" ], "package_name": "mail-parser", "purl": "pkg:pypi/mail-parser" } ], "cwes": [ 345 ], "cvss_score": 7.5, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "epss_score": 0.002, "epss_percentile": 0.1017, "epss_asof": "2026-11-17", "automation": "contextual", "check": true, "check_confidence_basis": "assessed", "exploit": false, "pipeline_minutes": 9.159472966666666, "t0_at": "2026-11-16T17:39:47.311000+00:00", "signals": { "check": { "at": "2026-11-16T18:08:13.834873+00:00", "days": 0.019751433715277777, "is_lower_bound": false, "measured_at": "2026-11-16T17:39:47.311000+00:00", "url": null }, "trigger_signal": { "at": "2026-11-16T17:39:47.311000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-11-16T17:39:47.311000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-129297" } } }
published 2026-11-16 17:58Z
last change 2026-11-18 21:43Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.