CVE-2025-15366

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (34th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
5.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The imaplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
27
EG Risk 27/100

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 (value × EchelonGraph’s weight)
Severity59% × 45%
The EG Score, 5.9 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

January 20, 2026

Last Modified

August 6, 2026

Advisory Details (6)

Auto-updated Jul 7, 2026
Patch available. Sources: github_commit, github_pr.
Web page

Mailman 3 [CVE-2025-15366] IMAP command injection in user-controlled commands - Security-announce - python.org

https://mail.python.org/archives/list/[email protected]/thread/DD7C7JZJYTBXMDOWKCEIEBJLBRU64OMR/
GitHub pull request

gh-143921: Reject control characters in IMAP commands

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

https://github.com/python/cpython/pull/143922
Web page

Reject control characters in IMAP commands · Issue #143921 · python/cpython · GitHub

https://github.com/python/cpython/issues/143921
GitHub commit

commit f2cd7ef89aa8 (python/cpython)

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

https://github.com/python/cpython/commit/f2cd7ef89aa8a0dcbc7283bbd39548b76f2a736a
GitHub commit

commit d0921efb665a (python/cpython)

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

https://github.com/python/cpython/commit/d0921efb665aff26b378f495e5ff84f7e3fe649d
GitHub commit

commit 6262704b134d (python/cpython)

Fix landed in python/cpython commit 6262704b134d — awaiting tagged release

https://github.com/python/cpython/commit/6262704b134db2a4ba12e85ecfbd968534f28b45

Vendor Advisories for CVE-2025-15366(20)

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

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhaiis/vllm-spyre-rhel9:17782445462026-05-12redhat
redhatpython3-14-main-3.14.4-2.hum12026-04-21redhat
redhatrhaiis/model-opt-cuda-rhel9:17757498572026-04-17redhat
redhatrhaiis/vllm-cuda-rhel9:17756801922026-04-17redhat
redhatpython3-12-main-3.12.13-3.hum12026-04-17redhat
redhatrhaiis/vllm-rocm-rhel9:17756802622026-04-17redhat
redhatpython3-11-main-3.11.15-4.hum12026-04-17redhat
redhatdiscovery/discovery-ui-rhel9:17756759222026-04-09redhat
redhatpython3-0:3.6.8-21.el7_9.42026-04-02redhat
redhatpython3.11-0:3.11.7-1.el9_4.112026-03-31redhat
redhatpython-0:2.6.6-70.el6_10.22026-03-30redhat
redhatpython3-0:3.6.8-51.el8_8.132026-03-30redhat
redhatpython3-13-main-3.13.12-2.hum12026-03-27redhat
redhatrhceph/rhceph-8-rhel9:17740028672026-03-24redhat
redhatpython3.12-0:3.12.9-2.el10_0.72026-03-23redhat
redhatpython3-0:3.6.8-47.el8_6.112026-03-23redhat
redhatpython3.9-0:3.9.10-4.el9_0.92026-03-23redhat
redhatpython3.11-0:3.11.2-2.el9_2.102026-03-23redhat
redhatpython3-0:3.6.8-24.el8_2.62026-03-23redhat
redhatpython3.9-0:3.9.18-3.el9_4.112026-03-23redhat
redhatpython3.12-0:3.12.1-4.el9_4.112026-03-23redhat
redhatpython-0:2.7.5-94.el7_9.32026-03-23redhat
redhatpython3-0:3.6.8-39.el8_4.92026-03-23redhat
redhatpython3.9-0:3.9.16-1.el9_2.122026-03-23redhat
redhatpython3.9-0:3.9.21-2.el9_6.42026-03-23redhat
redhatpython3.11-0:3.11.2-2.el8_8.82026-03-19redhat
redhatrhui5/rhua-rhel9:17736701372026-03-18redhat
redhatpython3.12-0:3.12.12-3.el10_1.12026-03-17redhat
redhatpython3.12-0:3.12.9-1.el9_6.62026-03-17redhat
redhatpython3.12-0:3.12.12-3.el8_102026-03-12redhat

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

(15 across 5 ecosystems)
Debian:11(4)
PackageVulnerable rangeFix by version rangeDependents
jython2.7.2+repack1-3, 2.7.2+repack1-4, 2.7.2+repack1-5, 2.7.3+repack1-1
  • every version on: no fix on record
—
pypy37.3.10+dfsg-1 ... 7.3.9+dfsg-5 (53 versions)
  • every version on: no fix on record
—
python2.72.7.18-10 ... 2.7.18-9 (10 versions)
  • every version on: no fix on record
—
python3.93.9.2-1, 3.9.2-1+deb11u1, 3.9.2-1+deb11u2, 3.9.2-1+deb11u3, 3.9.2-1+deb11u4
  • every version up to 3.9.2-1+deb11u5: fixed in 3.9.2-1+deb11u5
—
Debian:14(4)
PackageVulnerable rangeFix by version rangeDependents
jython2.7.3+repack1-1
  • every version on: no fix on record
—
pypy37.3.19+dfsg-2 ... 7.3.23+dfsg-1 (11 versions)
  • every version on: no fix on record
—
python3.133.13.11-1 ... 3.13.9-1 (9 versions)
  • every version on: no fix on record
—
python3.143.14.0-1 ... 3.14.7-2 (26 versions)
  • every version on: no fix on record
—
Debian:12(3)
PackageVulnerable rangeFix by version rangeDependents
jython2.7.3+repack1-1
  • every version on: no fix on record
—
pypy37.3.11+dfsg-2 ... 7.3.23+dfsg-1 (29 versions)
  • every version on: no fix on record
—
python3.113.11.2-6 ... 3.11.9-1 (28 versions)
  • every version on: no fix on record
—
Debian:13(3)
PackageVulnerable rangeFix by version rangeDependents
jython2.7.3+repack1-1
  • every version on: no fix on record
—
pypy37.3.19+dfsg-2 ... 7.3.23+dfsg-1 (11 versions)
  • every version on: no fix on record
—
python3.133.13.11-1 ... 3.13.9-1 (13 versions)
  • every version on: no fix on record
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.14.7-r0: fixed in 3.14.7-r0
—

Weakness Classification(1)

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

Additional Vendor Advisories

(15)

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 11× in last 7d / 30× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 97 of 232 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 135 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-15366?
CVE-2025-15366 is a medium-severity vulnerability; its CVE record was published on January 20, 2026. The imaplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters.
When was the CVE record for CVE-2025-15366 published?
The CVE record for CVE-2025-15366 was published on January 20, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 6, 2026; the record at its source may have been updated since.
Is CVE-2025-15366 actively exploited?
CVE-2025-15366 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-15366?
CVE-2025-15366 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-15366?
A fix for CVE-2025-15366 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-15366 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-15366?

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

Book a Demo →Browse All CVEs