CVE-2026-54903

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 83% 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
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.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.2, Oj.load is vulnerable to heap corruption when parsing a JSON string longer than 2 GB. An integer overflow in buf_append_string (buf.h:61) converts the string length to a large negative size_t, causing memcpy to copy an astronomically large amount of data out of bounds. This crashes the process and can corrupt adjacent heap memory. The issue has been fixed in version 3.17.2.

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

Published

June 19, 2026

Last Modified

July 1, 2026

Advisory Details (1)

Auto-updated Jul 1, 2026
Patch available. Sources: github.
github Patch Available

DFVULN-858: Integer Overflow in Oj.load 2GB String Handling · Advisory · ohler55/oj · GitHub

https://github.com/ohler55/oj/security/advisories/GHSA-475m-ph3x-64gp

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

Frequently asked(5)

What is CVE-2026-54903?
CVE-2026-54903 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.2, Oj.load is vulnerable to heap corruption when parsing a JSON string longer than 2 GB. An integer overflow in bufappendstring (buf.h:61) converts the string length to a large negative…
When was CVE-2026-54903 disclosed?
CVE-2026-54903 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-54903 actively exploited?
CVE-2026-54903 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 82.9% of all scored CVEs.
What is the CVSS score of CVE-2026-54903?
CVE-2026-54903 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-54903?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54903, 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-54903

Explore →

Is Your Infrastructure Affected by CVE-2026-54903?

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