CVE-2026-54696

LOWPre-NVD 3.73.7—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 3.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 3.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Ruby JSON is a JSON implementation for Ruby. Versions 2.9.0 through 2.19.8 are vulnerable to heap buffer overflow when the JSON generator is provided with an oversized streamed object. When streaming to an IO JSON.dump(obj, io) and JSON::State#generate(obj, io) can write past the internal JSON generator buffer when a streamed object contains an attacker-controlled string near 16 KB. Exploitation would result in a reliable process crash/denial of service. This issue has been fixed in version 2.19.9.

CVSS v3
3.7
EG Score
3.7LOWmedium confidence
EG Risk
21
EG Risk 21/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity37% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.4%
EPSS %ILE
30th
KEV
Not listed

Published

June 30, 2026

Last Modified

July 2, 2026

References (3)

Vendor Advisories for CVE-2026-54696(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatruby3-4-main-3.4.10-31.5.hum12026-07-30redhat
redhatruby4-0-main-4.0.6-37.1.hum12026-07-29redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-json2.15.2+dfsg-1 ... 3.0.2+dfsg-1 (10 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-json2.15.2+dfsg-1 ... 2.9.1+dfsg-1 (6 versions)
  • every version up to 2.19.9+dfsg-1: fixed in 2.19.9+dfsg-1
—
RubyGems(1)
PackageVulnerable rangeFix by version rangeDependents
json2.10.0 ... 2.9.1 (36 versions)
  • 2.9.0 up to 2.19.9: fixed in 2.19.9
—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 132 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-02 17:56 UTCEPSS rescore
  9. 2026-10-01 19:50 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-29 15:22 UTCEPSS rescore
  12. 2026-09-28 13:51 UTCEPSS rescore
  13. 2026-09-27 13:48 UTCEPSS rescore
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-24 14:04 UTCEPSS rescore
  16. 2026-09-23 17:54 UTCEPSS rescore
  17. 2026-09-23 07:05 UTCEG score recompute
  18. 2026-09-23 07:05 UTCVendor advisory
  19. 2026-09-20 20:16 UTCEPSS rescore
  20. 2026-09-18 19:28 UTCEPSS rescore
  21. 2026-09-18 06:40 UTCEG score recompute
  22. 2026-09-18 06:40 UTCVendor advisory
  23. 2026-09-17 19:31 UTCEPSS rescore
  24. 2026-09-16 14:08 UTCEPSS rescore
  25. 2026-09-16 05:15 UTCEPSS rescore
Show 75 more
  1. 2026-09-15 03:11 UTCEPSS rescore
  2. 2026-09-13 16:47 UTCEPSS rescore
  3. 2026-09-12 14:54 UTCEG score recompute
  4. 2026-09-12 14:54 UTCVendor advisory
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-10 09:35 UTCEPSS rescore
  7. 2026-09-08 22:01 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-06 05:05 UTCEG score recompute
  11. 2026-09-06 05:05 UTCVendor advisory
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:12 UTCEPSS rescore
  14. 2026-09-01 13:54 UTCEPSS rescore
  15. 2026-09-01 04:40 UTCEPSS rescore
  16. 2026-08-30 21:53 UTCEG score recompute
  17. 2026-08-30 21:53 UTCVendor advisory
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 22:32 UTCEG score recompute
  22. 2026-08-27 22:32 UTCVendor advisory
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 13:49 UTCEPSS rescore
  26. 2026-08-23 00:19 UTCEPSS rescore
  27. 2026-08-22 10:28 UTCEG score recompute
  28. 2026-08-22 10:28 UTCVendor advisory
  29. 2026-08-21 23:49 UTCEPSS rescore
  30. 2026-08-20 22:55 UTCEPSS rescore
  31. 2026-08-19 17:04 UTCEPSS rescore
  32. 2026-08-19 11:10 UTCEG score recompute
  33. 2026-08-19 11:10 UTCVendor advisory
  34. 2026-08-18 13:48 UTCEPSS rescore
  35. 2026-08-17 13:47 UTCEPSS rescore
  36. 2026-08-16 14:56 UTCEPSS rescore
  37. 2026-08-16 11:50 UTCEG score recompute
  38. 2026-08-16 11:50 UTCVendor advisory
  39. 2026-08-16 02:14 UTCEPSS rescore
  40. 2026-08-15 01:30 UTCEPSS rescore
  41. 2026-08-13 22:00 UTCEPSS rescore
  42. 2026-08-13 12:32 UTCEG score recompute
  43. 2026-08-13 12:32 UTCVendor advisory
  44. 2026-08-12 13:51 UTCEPSS rescore
  45. 2026-08-11 00:00 UTCEPSS rescore
  46. 2026-08-10 13:09 UTCEG score recompute
  47. 2026-08-10 13:09 UTCVendor advisory
  48. 2026-08-09 13:46 UTCEPSS rescore
  49. 2026-08-08 16:37 UTCEPSS rescore
  50. 2026-08-07 13:52 UTCEG score recompute
  51. 2026-08-07 13:52 UTCVendor advisory
  52. 2026-08-06 13:47 UTCEPSS rescore
  53. 2026-08-05 19:17 UTCEPSS rescore
  54. 2026-08-04 15:10 UTCEPSS rescore
  55. 2026-08-04 14:35 UTCEG score recompute
  56. 2026-08-04 14:35 UTCVendor advisory
  57. 2026-08-04 10:39 UTCEPSS rescore
  58. 2026-08-03 10:36 UTCEPSS rescore
  59. 2026-08-02 02:27 UTCEPSS rescore
  60. 2026-08-01 12:10 UTCEG score recompute
  61. 2026-08-01 12:10 UTCVendor advisory
  62. 2026-08-01 04:16 UTCEPSS rescore
  63. 2026-07-30 16:28 UTCEPSS rescore
  64. 2026-07-30 01:30 UTCEPSS rescore
  65. 2026-07-29 12:53 UTCEG score recompute
  66. 2026-07-28 15:37 UTCEPSS rescore
  67. 2026-07-26 14:54 UTCEPSS rescore
  68. 2026-07-26 13:35 UTCEG score recompute
  69. 2026-07-25 14:18 UTCEPSS rescore
  70. 2026-07-24 14:18 UTCEPSS rescore
  71. 2026-07-23 14:18 UTCEPSS rescore
  72. 2026-07-23 03:19 UTCEG score recompute
  73. 2026-07-22 14:08 UTCEPSS rescore
  74. 2026-07-21 15:25 UTCEPSS rescore
  75. 2026-07-20 17:08 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-54696?
CVE-2026-54696 is a low vulnerability published on June 30, 2026. Ruby JSON is a JSON implementation for Ruby. Versions 2.9.0 through 2.19.8 are vulnerable to heap buffer overflow when the JSON generator is provided with an oversized streamed object. When streaming to an IO JSON.dump(obj, io) and JSON::State#generate(obj, io) can write past the internal JSON…
When was CVE-2026-54696 disclosed?
CVE-2026-54696 was first published on June 30, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54696 actively exploited?
CVE-2026-54696 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54696?
CVE-2026-54696 has a CVSS base score of 3.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54696?
A fix for CVE-2026-54696 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54696 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54696

Explore →

Is Your Infrastructure Affected by CVE-2026-54696?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs