Skip to main content
VulnerabilityPublished Updated

CVE-2026-54696: Ruby json · JSON generator heap buffer overflow when streaming to an IO

Affects rubocopSource GCVE Database

0
Compare
Authoritative record:CVE-2026-54696· Low 3.7

Not known to be exploited · CVSS 3.7 Low : upgrade to 1.92.3 when convenient.

Data as of 18 Nov 2026, 18:04 UTC

CVSS 3.1 base score
3.7Low
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.92.3
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade rubocop to 1.92.3.

Affected software

ProductAffectedFixed in
Homebrewrubocoppkg:brew/rubocopOther threatsAffected
  • >=1.89.0 <1.92.3
Fixed in
  • 1.92.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and the issue is fixed in Ruby JSON version 1.92.3. Users should upgrade to version 1.92.3 or later to remediate this vulnerability.

Description

A heap buffer overflow vulnerability exists in Ruby's JSON generator when streaming JSON output to an IO object using JSON.dump(obj, io) or JSON::State#generate(obj, io). The flaw occurs due to incorrect buffer capacity checks, allowing an out-of-bounds write when processing attacker-controlled strings near 16 KB in size. This leads to a reliable denial of service via process crash. The issue affects Ruby JSON versions prior to 1.92.3 and has been fixed in version 1.92.3.

References

Community reviews

Loading reviews…