oj

CVE-2026-54897

CVE-2026-54897 is a high-severity use after free vulnerability in oj (rubygems), affecting versions < 3.17.2. It is fixed in 3.17.3.

Key facts
CVSS score
N/A
High
Attack vector
Not available
Issuing authority
GitHub Advisory Database
Affected package
oj
Fixed in
3.17.3
Disclosed
2026

Summary

Summary Oj::Doc iterators (eachvalue, eachchild, eachleaf) are vulnerable to a heap use-after-free. When a Ruby block yielded during iteration calls doc.close or d.close, the document's heap memory is freed while the C iterator is still running. When control returns from the block, the iterator reads from the freed region, producing a use-after-free accessible from pure Ruby. Version Software: oj gem Affected: all versions with ext/oj/fast.c Latest tested: 3.17.1 (confirmed present) Details The iterators in ext/oj/fast.c follow the pattern: rbyield can invoke arbitrary Ruby code, including calling close() on the Doc or any child node, which calls rubysizedxfree on the backing buffer. On return, the C code reads cur->next from the freed region. All three iterators are affected. ASAN report (each_child variant): All three iterators trigger the same freed region (fd shadow bytes): Reproduce

Impact

What is use after free?

Memory is accessed after it has been freed, leading to undefined behavior in native code. Typical impact: memory corruption, crash, or potential code execution.

Affected versions

rubygems

  • oj (< 3.17.2)

Security releases

  • oj → 3.17.3 (rubygems)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-54897 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-54897 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2026-54897 in your environment

Remediation advice

Upgrade oj to 3.17.3 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-54897

What is CVE-2026-54897?

CVE-2026-54897 is a high-severity use after free vulnerability in oj (rubygems), affecting versions < 3.17.2. It is fixed in 3.17.3. Memory is accessed after it has been freed, leading to undefined behavior in native code.

Which versions of oj are affected by CVE-2026-54897?

oj (rubygems) versions < 3.17.2 is affected.

Is there a fix for CVE-2026-54897?

Yes. CVE-2026-54897 is fixed in 3.17.3. Upgrade to this version or later.

Is CVE-2026-54897 exploitable, and should I be worried?

Whether CVE-2026-54897 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-54897 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-54897?

Upgrade oj to 3.17.3 or later.

Stop the waste.
Protect your environment with Kodem.