You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Out-of-memory when reading a HTTP response with large Content-Length #119451
http.client.HTTPResponse.read() (without argument) consumes the amount of memory specified by the value of the Content-Lenght header in the response before starting receiving the data from the socket. Normally, if the server does not send enough data, the client gets IncompleteRead error, but if Content-Lenght is too large, it can consume a large amount of memory and CPU time and cause swapping. Therefore, a maleficent server can cause a DOS attack on client by sending a small response.
Activity
pythongh-119451: Fix OOM vulnerability in http.client
25 remaining items
00472: CVE-2025-13836
CVE-2025-13836 python/cpython#119451
CVE-2025-13836 python/cpython#119451
lang/python314: security update to 3.14.2
lang/python314: security update to 3.14.2
[H p] Fix: OutOfMemory error in mirror Lambda function (#7730)
[H R] Fix: OutOfMemory error in mirror Lambda function (#7730)
[H R] Fix: OutOfMemory error in mirror Lambda function (#7730)
[H R] Fix: OutOfMemory error in mirror Lambda function (#7730)
[H R] Fix: OutOfMemory error in mirror Lambda function (#7730)
[CVE-2025-13836] Fix a potential denial of service in http.client
[CVE-2025-13836] Fix a potential denial of service in http.client
[CVE-2025-13836] Fix a potential denial of service in http.client
[CVE-2025-13836] Fix a potential denial of service in http.client