Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Search

GHSA-72px-j8gh-p79x

HighCVSS 7.5 / 10
Published Nov 16, 2026·Last modified Nov 16, 2026
Affected Components(1)
PyPI logomail-parser
< 4.6.2
Description

Patches

Fixed in 4.6.2. Upgrade with pip install --upgrade mail-parser.

Candidate addresses are now selected by position, not by appearance — a bracketed address the sender wrote is byte-identical to one the MTA wrote, so no amount of pattern matching can tell them apart:

  • the first token of the from clause is the HELO name, whatever its shape, and is never a candidate;
  • an explicit HELO marker inside a comment group is sender text and is excluded;
  • a candidate must sit inside a ( / [ group;
  • IPv4 and IPv6 matches are merged positionally, never family-first;
  • the walk stops at the first trusted hop naming no address, rather than continuing into sender-written headers.

The IPv6 pattern was corrected to skip the IPv6: tag and to prefer the longest valid form.

Behaviour change. get_server_ipaddress() now returns None rather than an unreliable value in two cases that previously returned an address: a from clause consisting of a bare address with no HELO marker (indistinguishable from EHLO <that address>), and a trusted hop naming no address at all. Callers must handle None.

Workarounds

None within mail-parser. Callers who cannot upgrade should not treat the return value of get_server_ipaddress() as trustworthy, and should derive sender attribution from an authenticated signal instead — the MTA's own logs, or SPF/DKIM/DMARC results computed outside this library.

Upload your SBOM

Upload your own SBOM in CycloneDX 1.6 or higher (JSON) directly here to check your vulnerabilities.

Risk Scores
Base Score
7.5

The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the integrity of the data.

Threat Intelligence
6.9

Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.

EPSS
0.20%

The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Browse More

Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard