Skip to content

Update json to 2.21.2 for CVE-2026-71847 - #110

Open
ultimatecoder wants to merge 1 commit into
masterfrom
fix/json-cve-2026-71847
Open

Update json to 2.21.2 for CVE-2026-71847#110
ultimatecoder wants to merge 1 commit into
masterfrom
fix/json-cve-2026-71847

Conversation

@ultimatecoder

Copy link
Copy Markdown
Owner

What

One-line Gemfile.lock bump: json 2.21.1 -> 2.21.2.

Why

The ruby-advisory-db entry for CVE-2026-71847 landed on 2026-08-14 and turned CI red across the repo. bundler-audit is the first step in build-and-test, so the build and link-check never get a chance to run behind it — every open PR reports a failure that has nothing to do with its own changes, and the scheduled Monday SEO audit is affected too.

Name: json
Version: 2.21.1
CVE: CVE-2026-71847
Title: Ruby JSON - JSON::ResumableParser#partial_value dereferences a freed
       input buffer and crashes on truncated duplicate-key streams
Solution: update to '>= 2.21.2'

json is a transitive dependency, pulled in by jekyll (~> 2.6) and json-minify (> 0). Both constraints already permit 2.21.2, so no Gemfile change is needed — only the lockfile moves.

Verification

Run locally against this branch:

bundle exec bundler-audit check --update    No vulnerabilities found
./scripts/optimize-images --check           All images are within budget.
./scripts/test                              HTML-Proofer finished successfully.

Found while rebasing #25, which is blocked on this and will be rebased on top once this merges.

🤖 Generated with Claude Code

The ruby-advisory-db entry landed on 2026-08-14 and turned every CI run in
the repo red, including the Monday SEO audit. bundler-audit runs before the
build, so nothing after it gets a chance to execute.

json is transitive here, pulled in by jekyll (~> 2.6) and json-minify (> 0).
Both constraints already allow 2.21.2, so this is a lockfile bump with no
Gemfile change.

  Title: Ruby JSON - JSON::ResumableParser#partial_value dereferences a freed
         input buffer and crashes on truncated duplicate-key streams
  Solution: update to '>= 2.21.2'

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant