Oj (Optimized JSON) is a JSON parser and Object marshaller packaged as a Ruby gem. In versions prior to 3.17.2, Oj.dump is vulnerable to a stack-based buffer overflow when a large :indent value is provided by the developer. fill_indent in dump.h calls memset(indent_str, ' ', (size_t)opts->indent) without validating the size. When opts->indent is set to INT_MAX (2,147,483,647), the (size_t) cast preserves the large value and memset writes 2 GB into the stack-allocated out buffer (4,184 bytes), corrupting the stack and crashing the process. This issue has been fixed in version 3.17.2.
CVE-2026-54502
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
- 17.0%
- KEV
- Not listed
Published
June 19, 2026
Last Modified
July 1, 2026
Advisory Details (1)
Auto-updated Jul 1, 2026DFVULN-849: Stack Buffer Overflow in Oj.dump via Large Indent · Advisory · ohler55/oj · GitHub
https://github.com/ohler55/oj/security/advisories/GHSA-3v45-f3vh-wg7mVendor Advisories for CVE-2026-54502(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 08:21 UTCEG score recompute
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 06:58 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 05:33 UTCEG score recompute
- 2026-07-03 04:08 UTCEG score recompute
- 2026-07-02 02:45 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 19:36 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-121
- CVE-2012-10058EG 10.0CRITICAL
- CVE-2010-20113EG 9.8CRITICAL
- CVE-2010-20121EG 9.8CRITICAL
- CVE-2012-10060EG 9.8CRITICAL
- CVE-2012-10023EG 9.8CRITICAL
- CVE-2013-10042EG 9.8CRITICAL
- CVE-2012-10021EG 9.8CRITICAL
- CVE-2014-125117EG 9.8EPSS 91%CRITICAL
- CVE-2017-14854NVD 9.1EG 9.8EPSS 94%CRITICAL
- CVE-2015-1006EG 9.8EPSS 92%CRITICAL
Frequently asked(5)
What is CVE-2026-54502?
When was CVE-2026-54502 disclosed?
Is CVE-2026-54502 actively exploited?
What is the CVSS score of CVE-2026-54502?
How do I remediate CVE-2026-54502?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54502
Is Your Infrastructure Affected by CVE-2026-54502?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.