CVE-2026-54896

LOWPre-NVD 2.12.1—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% 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
2.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Oj (Optimized JSON) is a JSON parser and Object marshaller packaged as a Ruby gem. In versions prior to 3.17.2, when in object mode, Oj.dump is vulnerable to a heap buffer overflow when serializing Exception objects with a large :indent value. The serializer allocates a buffer sized for the object's attributes but does not account for the indent bytes added on each write. With indent: 5000, the accumulation of 5,000-byte indent strings overflows the 13,150-byte heap allocation, corrupting adjacent heap memory. This issue has been fixed in version 3.17.2.

CVSS v3
2.1
EG Score
2.1(medium)
EG Risk
14(Track)
EG Risk 14/100SSVC: Track

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
Severity21% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 19, 2026

Last Modified

July 1, 2026

References (2)

Vendor Advisories for CVE-2026-54896(1)

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

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
ruby-oj3.11.0-1 ... 3.17.4-1 (26 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
ruby-oj3.14.2-1 ... 3.17.4-1 (12 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
ruby-oj3.16.12-1 ... 3.17.4-1 (8 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
ruby-oj3.16.12-1 ... 3.17.1-1 (6 versions)3.17.3-1—
RubyGems(1)
PackageVulnerable rangeFixed inDependents
oj0.5 ... 3.9.2 (294 versions)3.17.3—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 35× 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.

  1. 2026-08-22 23:40 UTCEG score recompute
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 12:43 UTCEG score recompute
  6. 2026-08-18 13:48 UTCEPSS rescore
  7. 2026-08-16 14:56 UTCEPSS rescore
  8. 2026-08-16 11:43 UTCEG score recompute
  9. 2026-08-16 02:14 UTCEPSS rescore
  10. 2026-08-15 01:30 UTCEPSS rescore
  11. 2026-08-13 22:00 UTCEPSS rescore
  12. 2026-08-13 12:42 UTCEG score recompute
  13. 2026-08-12 13:51 UTCEPSS rescore
  14. 2026-08-11 00:00 UTCEPSS rescore
  15. 2026-08-10 13:32 UTCEG score recompute
  16. 2026-08-09 13:46 UTCEPSS rescore
  17. 2026-08-08 16:37 UTCEPSS rescore
  18. 2026-08-07 14:19 UTCEG score recompute
  19. 2026-08-06 13:47 UTCEPSS rescore
  20. 2026-08-05 19:17 UTCEPSS rescore
  21. 2026-08-04 15:19 UTCEG score recompute
  22. 2026-08-04 15:10 UTCEPSS rescore
  23. 2026-08-04 10:39 UTCEPSS rescore
  24. 2026-08-03 10:36 UTCEPSS rescore
  25. 2026-08-02 02:27 UTCEPSS rescore
Show 41 more
  1. 2026-08-01 14:52 UTCEG score recompute
  2. 2026-08-01 04:16 UTCEPSS rescore
  3. 2026-07-30 16:28 UTCEPSS rescore
  4. 2026-07-30 01:30 UTCEPSS rescore
  5. 2026-07-29 15:51 UTCEG score recompute
  6. 2026-07-28 15:37 UTCEPSS rescore
  7. 2026-07-26 16:49 UTCEG score recompute
  8. 2026-07-26 14:54 UTCEPSS rescore
  9. 2026-07-25 14:18 UTCEPSS rescore
  10. 2026-07-24 14:18 UTCEPSS rescore
  11. 2026-07-23 03:20 UTCEG score recompute
  12. 2026-07-22 14:08 UTCEPSS rescore
  13. 2026-07-21 15:25 UTCEPSS rescore
  14. 2026-07-20 17:08 UTCEPSS rescore
  15. 2026-07-19 14:31 UTCEPSS rescore
  16. 2026-07-19 14:31 UTCEPSS rescore
  17. 2026-07-18 10:04 UTCEPSS rescore
  18. 2026-07-16 17:03 UTCEPSS rescore
  19. 2026-07-15 16:57 UTCEPSS rescore
  20. 2026-07-15 16:57 UTCEPSS rescore
  21. 2026-07-15 02:00 UTCEPSS rescore
  22. 2026-07-15 02:00 UTCEPSS rescore
  23. 2026-07-13 22:31 UTCEPSS rescore
  24. 2026-07-11 08:27 UTCEPSS rescore
  25. 2026-07-11 08:27 UTCEPSS rescore
  26. 2026-07-09 19:10 UTCEPSS rescore
  27. 2026-07-09 19:10 UTCEPSS rescore
  28. 2026-07-08 15:16 UTCEPSS rescore
  29. 2026-07-08 15:16 UTCEPSS rescore
  30. 2026-07-07 13:46 UTCEPSS rescore
  31. 2026-07-07 13:46 UTCEPSS rescore
  32. 2026-07-06 16:27 UTCEPSS rescore
  33. 2026-07-06 16:27 UTCEPSS rescore
  34. 2026-07-06 02:23 UTCEPSS rescore
  35. 2026-07-06 02:23 UTCEPSS rescore
  36. 2026-07-04 06:31 UTCEPSS rescore
  37. 2026-07-04 06:31 UTCEPSS rescore
  38. 2026-07-01 15:07 UTCEPSS rescore
  39. 2026-07-01 01:24 UTCEG score recompute▲ 2.10
  40. 2026-07-01 01:19 UTCNVD updateCVSS v3 → 2.1 · CVSS v4 → 2.1 · severity → LOW
  41. 2026-06-19 20:22 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54896?
CVE-2026-54896 is a low vulnerability published on June 19, 2026. Oj (Optimized JSON) is a JSON parser and Object marshaller packaged as a Ruby gem. In versions prior to 3.17.2, when in object mode, Oj.dump is vulnerable to a heap buffer overflow when serializing Exception objects with a large :indent value. The serializer allocates a buffer sized for the…
When was CVE-2026-54896 disclosed?
CVE-2026-54896 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54896 actively exploited?
CVE-2026-54896 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.9% of all scored CVEs.
What is the CVSS score of CVE-2026-54896?
CVE-2026-54896 has a CVSS v3 base score of 2.1 (NVD).
How do I remediate CVE-2026-54896?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54896, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-54896?

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

Start Free Scan →Browse All CVEs