Repository navigation
fix: bump json to 2.19.9 for CVE-2026-54696 - #41
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
1 participant
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.
Security advisory CVE-2026-54696 (GHSA-x2f5-4prf-w687). No issue filed.
The json library locked in this project, version 2.19.4, has a heap buffer overflow: writing JSON to a stream can overflow memory and crash the process when a string is close to 16 KB. The library is only pulled in by the code linter, so the project's own runtime code never triggers it, but the vulnerable version was still installed for everyone working on it.
The lockfile now pins json 2.19.9, the first fixed release, and nothing else changes.