Skip to content
Noroxi
NVD / CVE Program· CNA PSF

CVE-2025-1795: Mishandling of comma during folding and unicode-encoding of email headers

Noroxi assessment

Priority: Monitor (action score 9/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.62% (FIRST EPSS); higher than 50% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Python Software Foundation CPython 3.10.17, 3.11.9, 3.12.3; cbl2 python3 3.9.19-12 on CBL Mariner 2.0 3.9.19-12; cbl2 python3 3.9.19-13 on CBL Mariner 2.0 3.9.19-12.

Low priority for now. Upgrade to Python Software Foundation CPython 3.10.17, 3.11.9, 3.12.3; cbl2 python3 3.9.19-12 on CBL Mariner 2.0 3.9.19-12; cbl2 python3 3.9.19-13 on CBL Mariner 2.0 3.9.19-12 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

During an address list folding when a separating comma ends up on a folded line and that line is to be unicode-encoded then the separator itself is also unicode-encoded. Expected behavior is that the separating comma remains a plan comma. This can result in the address header being misinterpreted by some mail servers.

LowCVSS 2.3 · v4.0—No exploit Fix available
Published
Feb 28, 2025
Updated
Jul 31, 2026
EPSS
0.6% · 50th percentile

Report tools

JSON

Action score

9

Monitor

Low priority for now.

CVSS
9 / 40 · 2.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.6%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · PSF
2.3
NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-1795

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for python software foundation records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (PSF). Independent of NVD's CPE analysis and usually ahead of it.

  • Python Software Foundation CPython

    • before 3.9.23affected · python
    • 3.10.0 and later · before 3.10.17affected · python
    • 3.11.0 and later · before 3.11.9affected · python
    • 3.12.0 and later · before 3.12.3affected · python
    • 3.13.0a1 and later · before 3.13.0a5affected · python

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:11pypy3before 7.3.5+dfsg-2+deb11u57.3.5+dfsg-2+deb11u5
Debian:11python3.9before 3.9.2-1+deb11u33.9.2-1+deb11u3
Debian:12pypy3from 0—
Debian:12python3.11before 3.11.2-6+deb12u63.11.2-6+deb12u6
Debian:13pypy3before 7.3.18+dfsg-17.3.18+dfsg-1
Debian:13python3.13before 3.13.0~b1-13.13.0~b1-1
openSUSE:Leap 15.6python311before 3.11.11-150600.3.21.13.11.11-150600.3.21.1
openSUSE:Leap 15.6python311-corebefore 3.11.11-150600.3.21.13.11.11-150600.3.21.1
openSUSE:Leap 15.6python311-documentationbefore 3.11.11-150600.3.21.13.11.11-150600.3.21.1
openSUSE:Leap 15.6python312before 3.12.9-150600.3.21.13.12.9-150600.3.21.1
openSUSE:Leap 15.6python312-corebefore 3.12.9-150600.3.21.13.12.9-150600.3.21.1
openSUSE:Leap 15.6python312-documentationbefore 3.12.9-150600.3.21.13.12.9-150600.3.21.1
openSUSE:Tumbleweedpython311before 3.11.11-4.13.11.11-4.1
openSUSE:Tumbleweedpython312before 3.12.9-2.13.12.9-2.1
openSUSE:Tumbleweedpython313before 3.13.2-3.13.13.2-3.1
SUSE:Linux Enterprise Module for Basesystem 15 SP6python311-corebefore 3.11.11-150600.3.21.13.11.11-150600.3.21.1
SUSE:Linux Enterprise Module for Public Cloud 15 SP4python311before 3.11.11-150400.9.49.13.11.11-150400.9.49.1
SUSE:Linux Enterprise Module for Public Cloud 15 SP4python311-corebefore 3.11.11-150400.9.49.13.11.11-150400.9.49.1
SUSE:Linux Enterprise Module for Python 3 15 SP6python311before 3.11.11-150600.3.21.13.11.11-150600.3.21.1
SUSE:Linux Enterprise Module for Python 3 15 SP6python312before 3.12.9-150600.3.21.13.12.9-150600.3.21.1
SUSE:Linux Enterprise Module for Python 3 15 SP6python312-corebefore 3.12.9-150600.3.21.13.12.9-150600.3.21.1
SUSE:Linux Enterprise Module for Python 3 15 SP7python313before 3.13.5-150700.4.11.13.13.5-150700.4.11.1
SUSE:Linux Enterprise Module for Python 3 15 SP7python313-corebefore 3.13.5-150700.4.11.13.13.5-150700.4.11.1
SUSE:Linux Micro 6.0python311before 3.11.11-1.13.11.11-1.1

+3

Same product

python software foundation: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-115557Distrust compromised intermediate certificates in ssl module
    37Monitor
  • CVE-2025-4517Arbitrary writes via tarfile realpath overflow
    37Monitor
  • CVE-2026-19445Use-after-free of a server-side SSLContext when sni_callback switches contexts
    36Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2025-0938Jan 31, 2025 · URL parser allowed square brackets in domain names
    25Monitor
  • ← EarlierCVE-2024-3220Feb 14, 2025 · Default mimetype known files writeable on Windows
    9Monitor
  • Later →CVE-2025-4516May 15, 2025 · Use-after-free in "unicode_escape" decoder with error handler
    23Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Python Software Foundation CPython3.10.17Vendor (CNA)
Python Software Foundation CPython3.11.9Vendor (CNA)
Python Software Foundation CPython3.12.3Vendor (CNA)
Python Software Foundation CPython3.13.0a5Vendor (CNA)
Python Software Foundation CPython3.9.23Vendor (CNA)
cbl2 python3 3.9.19-12 on CBL Mariner 2.03.9.19-12 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 python3 3.9.19-13 on CBL Mariner 2.03.9.19-12 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 python3 3.9.19-13 on CBL-Mariner 2.03.9.19-12 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:pypy37.3.18+dfsg-1 · Debian:13Package registry (OSV)
debian:python3.113.11.2-6+deb12u6 · Debian:12Package registry (OSV)
debian:python3.133.13.0~b1-1 · Debian:13Package registry (OSV)
debian:python3.93.9.2-1+deb11u3 · Debian:11Package registry (OSV)
opensuse:python3113.11.11-150600.3.21.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:python311-core3.11.11-150600.3.21.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:python311-documentation3.11.11-150600.3.21.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:python3123.12.9-150600.3.21.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:python312-core3.12.9-150600.3.21.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:python312-documentation3.12.9-150600.3.21.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:python3133.13.2-3.1 · openSUSE:TumbleweedPackage registry (OSV)
suse:python3113.11.11-150400.9.49.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP4Package registry (OSV)
suse:python3113.11.11-150600.3.21.1 · SUSE:Linux Enterprise Module for Python 3 15 SP6Package registry (OSV)
suse:python311-core3.11.11-150400.9.49.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP4Package registry (OSV)
suse:python311-core3.11.11-150600.3.21.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:python3123.12.9-150600.3.21.1 · SUSE:Linux Enterprise Module for Python 3 15 SP6Package registry (OSV)
suse:python312-core3.12.9-150600.3.21.1 · SUSE:Linux Enterprise Module for Python 3 15 SP6Package registry (OSV)
suse:python3133.13.5-150700.4.11.1 · SUSE:Linux Enterprise Module for Python 3 15 SP7Package registry (OSV)
suse:python313-core3.13.5-150700.4.11.1 · SUSE:Linux Enterprise Module for Python 3 15 SP7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
X

Weakness class (CWE)

CWE-116 · Improper Encoding or Escaping of Output

CVSS vector

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (9 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records