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.
Advisories

No advisories yet.

Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

Mon, 01 Dec 2025 19:15:00 +0000

Type Values Removed Values Added
References
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 01 Dec 2025 18:15:00 +0000

Type Values Removed Values Added
Description 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.
Title Excessive read buffering DoS in http.client
References
Metrics cvssV4_0

{'score': 6.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L'}


cve-icon MITRE

Status: PUBLISHED

Assigner: PSF

Published:

Updated: 2025-12-01T19:00:52.546Z

Reserved: 2025-12-01T17:54:40.759Z

Link: CVE-2025-13836

cve-icon Vulnrichment

Updated: 2025-12-01T18:32:42.784Z

cve-icon NVD

Status : Received

Published: 2025-12-01T18:16:04.200

Modified: 2025-12-01T19:15:49.770

Link: CVE-2025-13836

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.