Quick answers
- Is CVE-2026-54696 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54696 being exploited in the wild.
- How severe is CVE-2026-54696?
- Low severity, with a CVSS score of 3.7, published 30 June 2026.
- Which products and versions are affected?
- json (RubyGems) ECOSYSTEM:introduced=2.9.0,fixed=2.19.9.
- Is there a fix for CVE-2026-54696?
- Yes. json (RubyGems): upgrade to 2.19.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-54696 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-54696?
- Check whether you run json (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- json (RubyGems): upgrade to 2.19.9 or later
bundle update json
Technical details
A heap-based buffer overflow exists in the Ruby 'json' gem's IO-streaming path. The root cause is an incorrect capacity check in 'fbuffer_do_inc_capa()' within 'ext/json/fbuffer/fbuffer.h', where the code checks total capacity instead of remaining capacity before appending data. When an attacker-controlled string near 16 KB is processed via 'JSON.dump(obj, io)' or 'JSON::State#generate(obj, io)', it can trigger an out-of-bounds write. This leads to a reliable process crash (Denial of Service). The issue is specific to the IO-streaming path and is fixed in version 2.19.9.
Affected products
- Ruby json >= 2.9.0, < 2.19.9
Identifiers
- CVE-2026-54696
- GHSA-x2f5-4prf-w687
Timeline
- 2026-06-11: disclosed: Initial disclosure in ruby/json repository
- 2026-06-11: patched: Version 2.19.9 released
- 2026-06-30: advisory: NVD publication date
- 2026-07-23: advisory: GitHub Advisory published