Skip to main content
CVE-2025-1795VulnerabilityPublished Updated

During an address list folding when a separating comma ends up on a folded line and that line is to be unicode-encoded

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-1795· Low 2.3

Not known to be exploited · CVSS 2.3 Low.

Data as of 30 Oct 2026, 01:14 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Feb 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
PyPIcpythonpkg:pypi/cpythonOther threatsAffected
  • 3.10.0 – 3.13.0
4 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, users should be aware of potential email header misinterpretation issues related to this encoding behavior.

Description

A vulnerability exists in the handling of address list folding in email headers where a separating comma placed on a folded line is incorrectly unicode-encoded. This causes the separator comma to be encoded rather than remaining a plain comma, potentially leading to misinterpretation of the address header by some mail servers.

References

Community reviews

Loading reviews…