[3.10] gh-119342: Fix a potential denial of service in plistlib (GH-119343)#142151
Merged
pablogsal merged 1 commit intopython:3.10from Mar 2, 2026
Merged
Conversation
…pythonGH-119343) Reading a specially prepared small Plist file could cause OOM because file's read(n) preallocates a bytes object for reading the specified amount of data. Now plistlib reads large data by chunks, therefore the upper limit of consumed memory is proportional to the size of the input file. (cherry picked from commit 694922c) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
vivian-rook
pushed a commit
to wolfi-dev/advisories
that referenced
this pull request
Dec 11, 2025
python-3.10 Upstream Fix PR: python/cpython#142151 python-3.11 Upstream Fix PR: python/cpython#142150 python-3.12 Upstream Fix PR: python/cpython#142149 Related issues: https://github.com/chainguard-dev/CVE-Dashboard/issues/49073 https://github.com/chainguard-dev/CVE-Dashboard/issues/48783 https://github.com/chainguard-dev/CVE-Dashboard/issues/49656 Signed-off-by: Vivian Rook <vivian.rook@chainguard.dev>
github-merge-queue bot
pushed a commit
to wolfi-dev/advisories
that referenced
this pull request
Dec 11, 2025
python-3.10 Upstream Fix PR: python/cpython#142151 python-3.11 Upstream Fix PR: python/cpython#142150 python-3.12 Upstream Fix PR: python/cpython#142149 Related issues: https://github.com/chainguard-dev/CVE-Dashboard/issues/49073 https://github.com/chainguard-dev/CVE-Dashboard/issues/48783 https://github.com/chainguard-dev/CVE-Dashboard/issues/49656 Signed-off-by: Vivian Rook <vivian.rook@chainguard.dev>
|
Hey @serhiy-storchaka Do you have an estimated time for when this will be merged? |
encukou
approved these changes
Feb 10, 2026
|
Hello @serhiy-storchaka, we would appreciate an ETA on when this would be merged :) |
Member
|
Expected before the next 3.10 release, but that isn't scheduled yet. |
github-project-automation
bot
moved this from Todo
to Done
in Release and Deferred blockers 🚫
Member
I am planning a 3.10 and 3.11 security release soon. Thank you everyone for your patience! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reading a specially prepared small Plist file could cause OOM because file's read(n) preallocates a bytes object for reading the specified amount of data. Now plistlib reads large data by chunks, therefore the upper limit of consumed memory is proportional to the size of the input file. (cherry picked from commit 694922c)