Repository navigation
Consume qualified Brotli decoder fix in v0.8.22 - #14
Merged
Merged
Conversation
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.
Use the published, digest-pinned Ubuntu security backports 0.1.1 bundle to replace the already-installed libbrotli1 with its qualified official CVE-2026-111497 decoder fix. Preserve the package set, selected coreutils provider, application/build behavior, raw/effective reports and existing vulnerability policy.
Align the Linux release inputs and current README usage with v0.8.22. The shared bundle passed its native owning/ABI tests, both real provider installation fixtures and immutable publication/readback (PastureStack/server#373, publisher40175072213); this product must still pass its own normal runtime/security and required checks.
Validation: the source diff is restricted to the exact bundle pin, numeric release values and short current documentation; affected YAML/source contracts pass. No ledger, VEX exception, scanner flag, toolchain or application logic changes. Product publication remains subject to the normal protected merge and immutable publisher.