Process crash via unchecked dump indentation
Published Jun 30, 2026 · Updated Jun 30, 2026
Stack-based buffer overflow in Oj before 3.17.2 allows remote attackers to crash a Ruby process through a large dump indent value. fill_indent multiplies an unchecked integer indent by nesting depth and passes the resulting length to memset against the 4,184-byte stack-allocated out buffer. Exploitation requires an application path that forwards an attacker-controlled indent option to Oj.dump; the demonstrated consequence is process termination from stack corruption.
Summary
What happened
Stack-based buffer overflow in Oj before 3.17.2 allows remote attackers to crash a Ruby process through a large dump indent value. fill_indent multiplies an unchecked integer indent by nesting depth and passes the resulting length to memset against the 4,184-byte stack-allocated out buffer. Exploitation requires an application path that forwards an attacker-controlled indent option to Oj.dump; the demonstrated consequence is process termination from stack corruption.
The record
- CVE
- CVE-2026-54502
- Published
- Jun 30, 2026
- Updated
- Jun 30, 2026
- Vendor
- Peter Ohler
- Product
- Oj
- Classifications
- CWE-121, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 30, 2026CVE publishedPublication date reported by the CVE source.
- Jun 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.17.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Large-indent Oj.dump crash reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo