Skip to content

Conversation

@miss-islington
Copy link
Contributor

@miss-islingtonmiss-islington commented Dec 1, 2025

Reading the whole body of the HTTP response could cause OOM if
the Content-Length value is too large even if the server does not send
a large amount of data. Now the HTTP client reads large data by chunks,
therefore the amount of consumed memory is proportional to the amount
of sent data.
(cherry picked from commit 5a4c4a0)

Co-authored-by: Serhiy Storchaka storchaka@gmail.com

…thonGH-119454) Reading the whole body of the HTTP response could cause OOM if the Content-Length value is too large even if the server does not send a large amount of data. Now the HTTP client reads large data by chunks, therefore the amount of consumed memory is proportional to the amount of sent data. (cherry picked from commit 5a4c4a0) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
@Yhg1sYhg1s merged commit 289f29b into python:3.13Dec 5, 2025
41 checks passed
vivian-rook added a commit to wolfi-dev/advisories that referenced this pull request Dec 8, 2025
python-3.11 Upstream Fix PR: python/cpython#142141 python-3.12 Upstream Fix PR: python/cpython#142140 python-3.13 Upstream Fix PR: python/cpython#142139 python-3.13 Local Fix PR: wolfi-dev/os#75166 Signed-off-by: Vivian Rook <vivian.rook@chainguard.dev>
github-merge-queuebot pushed a commit to wolfi-dev/advisories that referenced this pull request Dec 8, 2025
python-3.11 Upstream Fix PR: python/cpython#142141 python-3.12 Upstream Fix PR: python/cpython#142140 python-3.13 Upstream Fix PR: python/cpython#142139 python-3.13 Local Fix PR: wolfi-dev/os#75166 Signed-off-by: Vivian Rook <vivian.rook@chainguard.dev>
@miss-islingtonmiss-islington deleted the backport-5a4c4a0-3.13 branch January 2, 2026 16:48
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type-securityA security issue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@miss-islington@Yhg1s@serhiy-storchaka