CVE-2025-11468

MEDIUMNVD 5.75.7—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.7 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 57% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.7Exploit: None knownExposed: 0

A fix is available — apply it.

When folding a long comment in an email header containing exclusively unfoldable characters, the parenthesis would not be preserved. This could be used for injecting headers into email messages where addresses are user-controlled and not sanitized.

CVSS v3
5.7
EG Score
5.7(medium)
EG Risk
26(Track)
EG Risk 26/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity57% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
45%
KEV
Not listed

Published

January 20, 2026

Last Modified

June 17, 2026

Advisory Details (9)

Auto-updated Aug 8, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
generic

Mailman 3 [CVE-2025-11468] Folding email comments of unfoldable characters doesn't preserve parenthesis - Security-announce - python.org

https://mail.python.org/archives/list/[email protected]/thread/FELSEOLBI2QR6YLG6Q7VYF7FWSGQTKLI/
github_pr

gh-143935: Email preserve parens when folding comments

Fix merged in python/cpython PR #143936 on 2026-01-19 — awaiting tagged release

https://github.com/python/cpython/pull/143936
generic

Fix folding of long comments of unfoldable characters in email headers · Issue #143935 · python/cpython · GitHub

https://github.com/python/cpython/issues/143935
github_commit

commit f73838683802 (python/cpython)

Fix landed in python/cpython commit f73838683802 — awaiting tagged release

https://github.com/python/cpython/commit/f738386838021c762efea6c9802c82de65e87796
github_commit

commit e9970f077240 (python/cpython)

Fix landed in python/cpython commit e9970f077240 — awaiting tagged release

https://github.com/python/cpython/commit/e9970f077240c7c670e8a6fc6662f2b30d3b6ad0
github_commit

commit a76e4cd62dd6 (python/cpython)

Fix landed in python/cpython commit a76e4cd62dd6 — awaiting tagged release

https://github.com/python/cpython/commit/a76e4cd62dd68e7cbe86e37e6ed988495a646b66
github_commit

commit 61614a5e5056 (python/cpython)

Fix landed in python/cpython commit 61614a5e5056 — awaiting tagged release

https://github.com/python/cpython/commit/61614a5e5056e4f61ced65008d4576f3df34acb6
github_commit

commit 17d1490aa97b (python/cpython)

Fix landed in python/cpython commit 17d1490aa97b — awaiting tagged release

https://github.com/python/cpython/commit/17d1490aa97bd6b98a42b1a9b324ead84e7fd8a2
github_commit

commit 003b8315669b (python/cpython)

Fix landed in python/cpython commit 003b8315669b — awaiting tagged release

https://github.com/python/cpython/commit/003b8315669b9f08b1010a49071f73f15f818094

Vendor Advisories for CVE-2025-11468(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3.9-venv (3.9.5-3ubuntu0~20.04.1+esm9) @ focal2026-06-08ubuntu
redhatpython3-11-main-3.11.15-4.hum12026-04-17redhat
redhatpython3-12-main-3.12.13-3.hum12026-04-17redhat
redhatpython3-14-main-3.14.4-1.hum12026-04-11redhat
redhatpython3-13-main-3.13.13-1.hum12026-04-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(9 across 4 ecosystems)
Debian:14(3)
PackageVulnerable rangeFixed inDependents
pypy37.3.19+dfsg-2, 7.3.20+dfsg-1, 7.3.20+dfsg-2, 7.3.20+dfsg-3, 7.3.20+dfsg-47.3.21+dfsg-1—
python3.133.13.11-1 ... 3.13.9-1 (6 versions)3.13.12-1—
python3.143.14.0-1 ... 3.14.2-1 (14 versions)3.14.3-1—
Debian:11(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.10+dfsg-1 ... 7.3.9+dfsg-5 (53 versions)——
python3.93.9.2-1, 3.9.2-1+deb11u1, 3.9.2-1+deb11u2, 3.9.2-1+deb11u3, 3.9.2-1+deb11u43.9.2-1+deb11u5—
Debian:12(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.11+dfsg-2 ... 7.3.23+dfsg-1 (29 versions)——
python3.113.11.2-6 ... 3.11.2-6+deb12u6 (7 versions)3.11.2-6+deb12u7—
Debian:13(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.19+dfsg-2 ... 7.3.23+dfsg-1 (11 versions)——
python3.133.13.5-23.13.5-2+deb13u1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 181 total refreshes for this CVE.

  1. 2026-08-31 06:19 UTCOSV refresh
  2. 2026-08-30 19:16 UTCEPSS rescore
  3. 2026-08-30 19:16 UTCEPSS rescore
  4. 2026-08-30 01:21 UTCEPSS rescore
  5. 2026-08-28 21:39 UTCEPSS rescore
  6. 2026-08-27 14:24 UTCEPSS rescore
  7. 2026-08-26 14:44 UTCEPSS rescore
  8. 2026-08-25 13:47 UTCEPSS rescore
  9. 2026-08-24 14:15 UTCEPSS rescore
  10. 2026-08-23 00:18 UTCEPSS rescore
  11. 2026-08-21 23:47 UTCEPSS rescore
  12. 2026-08-20 22:54 UTCEPSS rescore
  13. 2026-08-19 17:02 UTCEPSS rescore
  14. 2026-08-18 13:47 UTCEPSS rescore
  15. 2026-08-17 13:46 UTCEPSS rescore
  16. 2026-08-16 14:55 UTCEPSS rescore
  17. 2026-08-16 02:13 UTCEPSS rescore
  18. 2026-08-15 01:29 UTCEPSS rescore
  19. 2026-08-14 13:26 UTCEG score recompute
  20. 2026-08-14 13:26 UTCVendor advisory
  21. 2026-08-14 13:26 UTCGHSA enrichment
  22. 2026-08-13 21:59 UTCEPSS rescore
  23. 2026-08-12 13:49 UTCEPSS rescore
  24. 2026-08-10 23:58 UTCEPSS rescore
  25. 2026-08-09 19:07 UTCEG score recompute
Show 75 more
  1. 2026-08-09 19:07 UTCVendor advisory
  2. 2026-08-09 19:07 UTCGHSA enrichment
  3. 2026-08-09 13:45 UTCEPSS rescore
  4. 2026-08-08 16:35 UTCEPSS rescore
  5. 2026-08-08 00:09 UTCEG score recompute
  6. 2026-08-08 00:09 UTCVendor advisory
  7. 2026-08-08 00:09 UTCGHSA enrichment
  8. 2026-08-07 16:26 UTCEPSS rescore
  9. 2026-08-06 13:45 UTCEPSS rescore
  10. 2026-08-06 05:24 UTCEG score recompute
  11. 2026-08-06 05:24 UTCVendor advisory
  12. 2026-08-06 05:24 UTCGHSA enrichment
  13. 2026-08-05 19:16 UTCEPSS rescore
  14. 2026-08-05 19:16 UTCEPSS rescore
  15. 2026-08-04 15:08 UTCEPSS rescore
  16. 2026-08-04 10:37 UTCEPSS rescore
  17. 2026-08-03 10:35 UTCEPSS rescore
  18. 2026-08-02 22:46 UTCEG score recompute
  19. 2026-08-02 22:46 UTCVendor advisory
  20. 2026-08-02 22:46 UTCGHSA enrichment
  21. 2026-08-02 02:25 UTCEPSS rescore
  22. 2026-08-01 04:14 UTCEPSS rescore
  23. 2026-07-31 21:42 UTCOSV refresh
  24. 2026-07-30 16:26 UTCEPSS rescore
  25. 2026-07-30 01:29 UTCEPSS rescore
  26. 2026-07-28 15:35 UTCEPSS rescore
  27. 2026-07-27 14:12 UTCEPSS rescore
  28. 2026-07-26 14:53 UTCEPSS rescore
  29. 2026-07-25 14:17 UTCEPSS rescore
  30. 2026-07-25 14:17 UTCEPSS rescore
  31. 2026-07-23 14:17 UTCEPSS rescore
  32. 2026-07-23 02:48 UTCEG score recompute
  33. 2026-07-22 14:07 UTCEPSS rescore
  34. 2026-07-22 14:07 UTCEPSS rescore
  35. 2026-07-21 15:24 UTCEPSS rescore
  36. 2026-07-20 17:07 UTCEPSS rescore
  37. 2026-07-19 14:30 UTCEPSS rescore
  38. 2026-07-19 02:28 UTCEPSS rescore
  39. 2026-07-19 02:28 UTCEPSS rescore
  40. 2026-07-18 10:03 UTCEPSS rescore
  41. 2026-07-18 10:03 UTCEPSS rescore
  42. 2026-07-16 17:02 UTCEPSS rescore
  43. 2026-07-16 17:02 UTCEPSS rescore
  44. 2026-07-15 16:57 UTCEPSS rescore
  45. 2026-07-15 16:57 UTCEPSS rescore
  46. 2026-07-15 01:59 UTCEPSS rescore
  47. 2026-07-15 01:59 UTCEPSS rescore
  48. 2026-07-14 04:55 UTCOSV refresh
  49. 2026-07-13 22:29 UTCEPSS rescore
  50. 2026-07-13 22:29 UTCEPSS rescore
  51. 2026-07-13 06:12 UTCEPSS rescore
  52. 2026-07-12 05:45 UTCEPSS rescore
  53. 2026-07-12 05:45 UTCEPSS rescore
  54. 2026-07-11 08:26 UTCEPSS rescore
  55. 2026-07-09 19:09 UTCEPSS rescore
  56. 2026-07-09 19:09 UTCEPSS rescore
  57. 2026-07-08 15:14 UTCEPSS rescore
  58. 2026-07-07 13:45 UTCEPSS rescore
  59. 2026-07-06 16:26 UTCEPSS rescore
  60. 2026-07-06 16:26 UTCEPSS rescore
  61. 2026-07-06 02:22 UTCEPSS rescore
  62. 2026-07-05 02:30 UTCEPSS rescore
  63. 2026-07-04 06:30 UTCEPSS rescore
  64. 2026-07-04 06:30 UTCEPSS rescore
  65. 2026-07-02 17:00 UTCEPSS rescore
  66. 2026-07-01 15:06 UTCEPSS rescore
  67. 2026-06-30 23:21 UTCEPSS rescore
  68. 2026-06-28 14:07 UTCEPSS rescore
  69. 2026-06-28 14:07 UTCEPSS rescore
  70. 2026-06-28 04:55 UTCEPSS rescore
  71. 2026-06-28 04:55 UTCEPSS rescore
  72. 2026-06-27 03:08 UTCEPSS rescore
  73. 2026-06-26 02:16 UTCOSV refresh
  74. 2026-06-25 13:49 UTCEPSS rescore
  75. 2026-06-25 13:49 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-11468?
CVE-2025-11468 is a medium vulnerability published on January 20, 2026. When folding a long comment in an email header containing exclusively unfoldable characters, the parenthesis would not be preserved. This could be used for injecting headers into email messages where addresses are user-controlled and not sanitized.
When was CVE-2025-11468 disclosed?
CVE-2025-11468 was first published in the National Vulnerability Database on January 20, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-11468 actively exploited?
CVE-2025-11468 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 55.1% of all scored CVEs.
What is the CVSS score of CVE-2025-11468?
CVE-2025-11468 has a CVSS v3 base score of 5.7 (NVD).
How do I remediate CVE-2025-11468?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-11468, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-11468

Explore →

Is Your Infrastructure Affected by CVE-2025-11468?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs