Oj (Optimized JSON) is a JSON parser and Object marshaller packaged as a Ruby gem. Prior to version 3.17.2, is vulnerable to Use-After-Free when in SAJ mode. The Oj::Parser does not protect cached object keys (≥ 35 bytes) from garbage collection, and a Ruby callback that triggers GC inside hash_end can cause the key string to be reclaimed while the C parser still holds a pointer to it. The subsequent access to the freed string VALUE results in a segfault, confirmed by an RIP pointing to address 0x4242 (a canary-style pattern suggesting control over the freed memory's content). This issue has been fixed in version 3.17.2.
CVE-2026-54902
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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(medium)
- EPSS
- 16.6%
- KEV
- Not listed
Published
June 19, 2026
Last Modified
July 1, 2026
Advisory Details (1)
Auto-updated Jul 1, 2026DFVULN-856: Use-After-Free in Oj::Parser SAJ Long Key Callback · Advisory · ohler55/oj · GitHub
https://github.com/ohler55/oj/security/advisories/GHSA-m578-w5vf-rfcmVendor Advisories for CVE-2026-54902(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
RubyGems(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| oj | 0.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 16× in last 7d / 17× 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.
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 06:20 UTCEG score recompute
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 05:24 UTCEG score recompute
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 04:20 UTCEG score recompute
- 2026-07-03 03:14 UTCEG score recompute
- 2026-07-02 02:19 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 01:24 UTCEG score recompute▲ 6.30
- 2026-07-01 01:19 UTCNVD updateCVSS v3 → 6.3 · CVSS v4 → 6.3 · severity → MEDIUM
- 2026-06-19 21:24 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-416
- CVE-2010-3962NVD 8.1EG 9.0 KEVEPSS 100%HIGH
- CVE-2010-0806NVD 8.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2010-0249NVD 8.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2009-4324NVD 7.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2010-3328EG 8.8EPSS 98%HIGH
- CVE-2010-1772EG 8.8HIGH
- CVE-2010-1208EG 8.8EPSS 91%HIGH
- CVE-2010-0050EG 8.8EPSS 96%HIGH
- CVE-2010-0378EG 8.8EPSS 93%HIGH
- CVE-2009-3658EG 8.8EPSS 95%HIGH
Frequently asked(5)
What is CVE-2026-54902?
When was CVE-2026-54902 disclosed?
Is CVE-2026-54902 actively exploited?
What is the CVSS score of CVE-2026-54902?
How do I remediate CVE-2026-54902?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54902
Is Your Infrastructure Affected by CVE-2026-54902?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.