Repository navigation
Conversation
Author
|
I could not find an existing ORC JIRA for this dependency bump. Happy to file one if the project requires it before review. |
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.
Background
CVE-2026-111497 is an out-of-bounds write in the Google Brotli decoder, fixed in Brotli 1.2.1.
orc-coredecodes Brotli-compressed ORC streams throughBrotliCodec, which uses brotli4j 1.23.0. That release bundles Brotli 1.2.0 and is therefore still vulnerable when reading an untrusted ORC file.brotli4j 1.24.0 upgrades the bundled native decoder to Brotli 1.2.1:
Change
brotli4j.versionproperty from 1.23.0 to 1.24.0.No ORC API or file-format changes.
Testing
TestBrotli: 5 tests, 0 failures, 0 errors.