CVE-2025-15366

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 72% 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.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.9Exploit: NoneExposed: 0

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.9(medium)
EPSS
28.2%
KEV
Not listed

Published

January 20, 2026

Last Modified

July 9, 2026

Advisory Details (6)

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

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_pr

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
generic

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

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhaiis/vllm-spyre-rhel9:17782445462026-05-12redhat
redhatpython3-14-main-3.14.4-2.hum12026-04-21redhat
redhatrhaiis/vllm-rocm-rhel9:17756802622026-04-17redhat
redhatpython3-12-main-3.12.13-3.hum12026-04-17redhat
redhatpython3-11-main-3.11.15-4.hum12026-04-17redhat
redhatrhaiis/vllm-cuda-rhel9:17756801922026-04-17redhat
redhatrhaiis/model-opt-cuda-rhel9:17757498572026-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
redhatpython3-0:3.6.8-51.el8_8.132026-03-30redhat
redhatpython-0:2.6.6-70.el6_10.22026-03-30redhat
redhatpython3-13-main-3.13.12-2.hum12026-03-27redhat
redhatrhceph/rhceph-8-rhel9:17740028672026-03-24redhat
redhatpython3.9-0:3.9.21-2.el9_6.42026-03-23redhat
redhatpython3-0:3.6.8-39.el8_4.92026-03-23redhat
redhatpython3.9-0:3.9.18-3.el9_4.112026-03-23redhat
redhatpython3.9-0:3.9.10-4.el9_0.92026-03-23redhat
redhatpython3.12-0:3.12.1-4.el9_4.112026-03-23redhat
redhatpython3-0:3.6.8-47.el8_6.112026-03-23redhat
redhatpython-0:2.7.5-94.el7_9.32026-03-23redhat
redhatpython3-0:3.6.8-24.el8_2.62026-03-23redhat
redhatpython3.11-0:3.11.2-2.el9_2.102026-03-23redhat
redhatpython3.12-0:3.12.9-2.el10_0.72026-03-23redhat
redhatpython3.9-0:3.9.16-1.el9_2.122026-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.9-1.el9_6.62026-03-17redhat
redhatpython3.12-0:3.12.12-3.el10_1.12026-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.

Weakness Classification(1)

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

Additional Vendor Advisories

(15)

Data Freshness Timeline

(refreshed 15× in last 7d / 48× 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 116 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-15366?
CVE-2025-15366 is a medium vulnerability 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 CVE-2025-15366 disclosed?
CVE-2025-15366 was first published in the National Vulnerability Database on January 20, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-15366 actively exploited?
CVE-2025-15366 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 28.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-15366?
CVE-2025-15366 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2025-15366?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-15366, 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

Explore the affected products and dependency analysis for 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.