CVE-2026-54500

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 90% 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
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: 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.3, Oj.load in :object mode reads uninitialized stack memory (and, for long keys, reads out of bounds) when parsing a JSON object whose key is 254 bytes or longer. The interned bytes can surface to the caller, disclosing process stack memory. In ext/oj/intern.c, form_attr() handles the long-key path by allocating a heap buffer, b, populating it with the attribute name, and then freeing it — but it passed the uninitialized stack buffer buf (not b) to rb_intern3(). rb_intern3 therefore reads len + 1 bytes of uninitialized stack memory. When the key length is >= 256, it also reads out of bounds past the 256-byte buf. The resulting bytes are interned and can reach the caller via the produced Symbol or via the EncodingError message raised on invalid UTF-8, leaking process stack contents. This issue has been fixed in version 3.17.3.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
28(Track)
EG Risk 28/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
Severity53% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

June 19, 2026

Last Modified

July 1, 2026

Advisory Details (1)

Auto-updated Jul 1, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Uninitialized stack memory read in Oj.load object mode via long keys · Advisory · ohler55/oj · GitHub

https://github.com/ohler55/oj/security/advisories/GHSA-fm7p-mprw-wjm9

Vendor Advisories for CVE-2026-54500(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(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 50× 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:42 UTCEG score recompute
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-21 05:43 UTCEG score recompute
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 08:00 UTCEG score recompute
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 07:02 UTCEG score recompute
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-17 12:39 UTCEG score recompute
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-16 14:56 UTCEG score recompute
  13. 2026-08-16 02:14 UTCEPSS rescore
  14. 2026-08-15 17:13 UTCEG score recompute
  15. 2026-08-15 01:30 UTCEPSS rescore
  16. 2026-08-14 19:25 UTCEG score recompute
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-12 23:58 UTCEG score recompute
  19. 2026-08-12 13:51 UTCEPSS rescore
  20. 2026-08-12 02:16 UTCEG score recompute
  21. 2026-08-11 04:33 UTCEG score recompute
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-10 06:50 UTCEG score recompute
  24. 2026-08-09 13:46 UTCEPSS rescore
  25. 2026-08-09 09:08 UTCEG score recompute
Show 61 more
  1. 2026-08-08 16:37 UTCEPSS rescore
  2. 2026-08-08 11:25 UTCEG score recompute
  3. 2026-08-06 15:59 UTCEG score recompute
  4. 2026-08-06 13:47 UTCEPSS rescore
  5. 2026-08-05 19:17 UTCEPSS rescore
  6. 2026-08-04 15:19 UTCEG score recompute
  7. 2026-08-04 15:10 UTCEPSS rescore
  8. 2026-08-04 10:39 UTCEPSS rescore
  9. 2026-08-03 15:33 UTCEG score recompute
  10. 2026-08-03 10:36 UTCEPSS rescore
  11. 2026-08-02 17:49 UTCEG score recompute
  12. 2026-08-02 02:27 UTCEPSS rescore
  13. 2026-08-01 20:06 UTCEG score recompute
  14. 2026-08-01 04:16 UTCEPSS rescore
  15. 2026-07-31 00:38 UTCEG score recompute
  16. 2026-07-30 16:28 UTCEPSS rescore
  17. 2026-07-30 02:55 UTCEG score recompute
  18. 2026-07-30 01:30 UTCEPSS rescore
  19. 2026-07-29 01:35 UTCEG score recompute
  20. 2026-07-28 15:37 UTCEPSS rescore
  21. 2026-07-27 18:03 UTCEG score recompute
  22. 2026-07-26 16:49 UTCEG score recompute
  23. 2026-07-26 14:54 UTCEPSS rescore
  24. 2026-07-25 14:18 UTCEPSS rescore
  25. 2026-07-24 14:18 UTCEPSS rescore
  26. 2026-07-23 14:18 UTCEPSS rescore
  27. 2026-07-23 03:19 UTCEG score recompute
  28. 2026-07-22 14:08 UTCEPSS rescore
  29. 2026-07-21 15:25 UTCEPSS rescore
  30. 2026-07-20 17:08 UTCEPSS rescore
  31. 2026-07-19 14:31 UTCEPSS rescore
  32. 2026-07-19 14:31 UTCEPSS rescore
  33. 2026-07-19 02:29 UTCEPSS rescore
  34. 2026-07-18 10:04 UTCEPSS rescore
  35. 2026-07-16 17:03 UTCEPSS rescore
  36. 2026-07-15 16:57 UTCEPSS rescore
  37. 2026-07-15 16:57 UTCEPSS rescore
  38. 2026-07-15 02:00 UTCEPSS rescore
  39. 2026-07-15 02:00 UTCEPSS rescore
  40. 2026-07-13 22:31 UTCEPSS rescore
  41. 2026-07-13 06:13 UTCEPSS rescore
  42. 2026-07-13 06:13 UTCEPSS rescore
  43. 2026-07-12 05:46 UTCEPSS rescore
  44. 2026-07-11 08:27 UTCEPSS rescore
  45. 2026-07-11 08:27 UTCEPSS rescore
  46. 2026-07-09 19:10 UTCEPSS rescore
  47. 2026-07-09 19:10 UTCEPSS rescore
  48. 2026-07-08 15:16 UTCEPSS rescore
  49. 2026-07-08 15:16 UTCEPSS rescore
  50. 2026-07-07 13:46 UTCEPSS rescore
  51. 2026-07-07 13:46 UTCEPSS rescore
  52. 2026-07-06 16:27 UTCEPSS rescore
  53. 2026-07-06 16:27 UTCEPSS rescore
  54. 2026-07-06 02:23 UTCEPSS rescore
  55. 2026-07-06 02:23 UTCEPSS rescore
  56. 2026-07-05 02:31 UTCEPSS rescore
  57. 2026-07-05 02:30 UTCEPSS rescore
  58. 2026-07-04 06:31 UTCEPSS rescore
  59. 2026-07-04 06:31 UTCEPSS rescore
  60. 2026-07-01 15:07 UTCEPSS rescore
  61. 2026-06-19 20:22 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54500?
CVE-2026-54500 is a medium 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.3, Oj.load in :object mode reads uninitialized stack memory (and, for long keys, reads out of bounds) when parsing a JSON object whose key is 254 bytes or longer. The interned bytes can…
When was CVE-2026-54500 disclosed?
CVE-2026-54500 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-54500 actively exploited?
CVE-2026-54500 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 90.1% of all scored CVEs.
What is the CVSS score of CVE-2026-54500?
CVE-2026-54500 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-54500?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54500, 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-54500

Explore →

Is Your Infrastructure Affected by CVE-2026-54500?

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

Start Free Scan →Browse All CVEs