Bump json to patched version, fixing CVE-2026-54696 (v2.2.1) - #130
Merged
Conversation
json 2.9.0 through 2.19.8 has a heap buffer overflow when the generator streams an object containing a large string to an IO (GHSA-x2f5-4prf-w687). Raise the gemspec's minimum json constraint to the patched 2.19.9 and update Gemfile.lock accordingly (resolves to 2.21.1). The existing `~> 2.0` upper bound already permitted this version, so no constraint widening was needed.
Prepares the 2.2.1 patch release: bumps Tree::VERSION, updates the self-referential Gemfile.lock entry, adds the History.md release note for the json CVE-2026-54696 fix, and refreshes the copyright year range.
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.
Summary
jsonruntime dependency's minimum constraint to>= 2.19.9, fixing CVE-2026-54696 / GHSA-x2f5-4prf-w687 (heap buffer overflow when generating to a streamed IO);Gemfile.lockresolves to 2.21.1Tree::VERSIONto2.2.1, add theHistory.mdrelease note, and refresh the copyright year range inlib/tree/version.rbContext
master'sGemfile.lockwas resolvingjson (2.9.1), which falls in the vulnerable range (2.9.0-2.19.8). The gemspec's existing~> 2.0upper bound already permitted the patched version, so no constraint widening was needed — just a lower-bound bump and abundle update json.This is intended as the first real end-to-end test of the trusted-publishing release workflow added in #129: once merged, we'll tag
R2.2.1onmasterto trigger the OIDC publish to RubyGems.org, then cherry-pick both commits intonext.Test plan
rake test:allpasses (96 tests / 36 examples, 0 failures)rake gem:packagebuildsrubytree-2.2.1.gemsuccessfullyrake versionreportsrubytree-2.2.1.gemR2.2.1is tagged after merge