Repository navigation
Conversation
This branch has not been deployed
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
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.
Why
CVE-2026-111497 is an out-of-bounds write in the Brotli decoder that allows remote code execution through a crafted br-compressed stream. The PyPI
Brotlipackage up to 1.2.0 andbrotlicffi1.2.0.x carry the same decoder. Both are fixed in Brotli 1.2.1 and brotlicffi 1.2.1.0. (Node.js is affected too, but this repo has no Node version pins, so this PR only covers the Python packages.)What changed
uv.lock:brotli1.2.0 to 1.2.1, viauv lock --upgrade-package brotli --upgrade-package brotlicffiwith uv 0.10.9 (the newest uv the workflows pin). No other packages changed. brotlicffi is not in this lock.How I verified it
uv lock --locked(uv 0.10.9): passes.uv sync --locked(uv 0.10.9): passes;python -c "import brotli; print(brotli.__version__)"prints1.2.1.pre-commit run --files uv.lock: all hooks pass, includinguv-lock.tests/tool_tests/test_integration.py) holds integration tests that need API keys and services I do not have (they error on missing config), and pytest is commented out inunit_tests.yml.Deploy impact
No app deploy on merge.
docs.ymlruns on push to main whenuv.lockchanges and redeploys the docs site to GitHub Pages. PyPI publishing runs only on a published release.