CVE-2025-13836

CRITICALNVD 7.59.1▲
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory published 2025-12-01. NVD baseline CVSS 7.5; sources differ by 1.6.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

When reading an HTTP response from a server, if no read amount is specified, the default behavior will be to use Content-Length. This allows a malicious server to cause the client to read large amounts of data into memory, potentially causing OOM or other DoS.

CVSS v3
7.5
EG Score
9.1(medium)
EG Risk
42(Track)
EG Risk 42/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
Severity91% × 45%
Exploitation2% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
72%
KEV
Not listed

Published

December 1, 2025

Last Modified

May 18, 2026

Advisory Details (9)

Auto-updated May 18, 2026
No patch confirmed yet.
generic

Mailman 3 [CVE-2025-13836] Excessive read buffering DoS in http.client - Security-announce - python.org

https://mail.python.org/archives/list/[email protected]/thread/OQ6G7MKRQIS3OAREC3HNG3D2DPOU34XO/
generic

gh-119451: Fix a potential denial of service in http.client by serhiy-storchaka · Pull Request #119454 · python/cpython · GitHub

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

Out-of-memory when reading a HTTP response with large Content-Length · Issue #119451 · python/cpython · GitHub

https://github.com/python/cpython/issues/119451
generic

[3.11] gh-119451: Fix a potential denial of service in http.client (G… · python/cpython@afc40bd · GitHub

https://github.com/python/cpython/commit/afc40bdd3dd71f343fd9016f6d8eebbacbd6587c
generic

[3.10] gh-119451: Fix a potential denial of service in http.client (G… · python/cpython@5dc1016 · GitHub

https://github.com/python/cpython/commit/5dc101675fd22918facbbe0fecdc821502beaaf0
generic

gh-119451: Fix a potential denial of service in http.client (GH-119454) · python/cpython@5a4c4a0 · GitHub

https://github.com/python/cpython/commit/5a4c4a033a4a54481be6870aa1896fad732555b5
generic

[3.14] gh-119451: Fix a potential denial of service in http.client (G… · python/cpython@4ce2790 · GitHub

https://github.com/python/cpython/commit/4ce27904b597c77d74dd93f2c912676021a99155
generic

[3.13] gh-119451: Fix a potential denial of service in http.client (G… · python/cpython@289f29b · GitHub

https://github.com/python/cpython/commit/289f29b0fe38baf2d7cb5854f4bb573cc34a6a15
generic

[3.12] gh-119451: Fix a potential denial of service in http.client (G… · python/cpython@14b1fdb · GitHub

https://github.com/python/cpython/commit/14b1fdb0a94b96f86fc7b86671ea9582b8676628

Vendor Advisories for CVE-2025-13836(13)

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

Patch Availability(24)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3.14-venv (3.14.0-1ubuntu0.1) @ questing2026-05-21ubuntu
redhatrhaiis/vllm-spyre-rhel9:17782445462026-05-12redhat
redhatrhaiis/vllm-rocm-rhel9:17756802622026-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
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
redhatrhui5/cds-rhel9:17736700732026-03-18redhat
redhatpython3.12-0:3.12.1-4.el9_4.102026-03-05redhat
redhatpython3.12-0:3.12.9-1.el9_6.52026-03-05redhat
redhatrhui5/rhua-rhel9:17708087652026-02-11redhat
redhatpython3.12-0:3.12.12-2.el8_102026-02-10redhat
redhatpython3.12-0:3.12.9-2.el10_0.62026-02-09redhat
redhatpython3.11-0:3.11.2-2.el8_8.72026-02-05redhat
redhatpython3.11-0:3.11.7-1.el9_4.102026-02-04redhat
redhatpython3.11-0:3.11.11-2.el9_6.42026-02-04redhat
redhatpython3.11-0:3.11.2-2.el9_2.92026-02-04redhat
redhatpython3.12-0:3.12.12-3.el10_12026-02-03redhat
redhatdiscovery/discovery-server-rhel9:17691047652026-02-02redhat
redhatpython3.11-0:3.11.13-5.el9_72026-01-27redhat
redhatpython3.12-0:3.12.12-4.el9_72026-01-27redhat
redhatpython3.11-0:3.11.13-4.el8_102026-01-27redhat

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

(12)

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 / 42× 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 122 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-13836?
CVE-2025-13836 is a critical vulnerability published on December 1, 2025. When reading an HTTP response from a server, if no read amount is specified, the default behavior will be to use Content-Length. This allows a malicious server to cause the client to read large amounts of data into memory, potentially causing OOM or other DoS.
When was CVE-2025-13836 disclosed?
CVE-2025-13836 was first published in the National Vulnerability Database on December 1, 2025, with the most recent update on May 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-13836 actively exploited?
CVE-2025-13836 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 28.0% of all scored CVEs.
What is the CVSS score of CVE-2025-13836?
CVE-2025-13836 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.1.
How do I remediate CVE-2025-13836?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-13836, 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-13836

Explore →

Is Your Infrastructure Affected by CVE-2025-13836?

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

Start Free Scan →Browse All CVEs