Excessive read buffering DoS in http.client
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-13836US | high7.5 | — | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/python/cpython/commit/14b1fdb0a94b96f86fc7b86671ea9582b8676628FIX
- https://github.com/python/cpython/commit/289f29b0fe38baf2d7cb5854f4bb573cc34a6a15FIX
- https://github.com/python/cpython/commit/4ce27904b597c77d74dd93f2c912676021a99155FIX
- https://github.com/python/cpython/commit/5a4c4a033a4a54481be6870aa1896fad732555b5FIX
- https://github.com/python/cpython/commit/5dc101675fd22918facbbe0fecdc821502beaaf0FIX
- https://github.com/python/cpython/commit/afc40bdd3dd71f343fd9016f6d8eebbacbd6587cFIX
- https://github.com/python/cpython/issues/119451FIX
- https://github.com/python/cpython/pull/119454FIX
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan