CVE-2026-54897 ohler55 CVE debrief

Who should care

Defenders responsible for RubyGems inventory management and oj gem usage should assess exposure and prioritize verification and remediation efforts. This includes operators, platform administrators, vulnerability management teams, and security teams who use the affected versions of the oj gem. They should verify the presence of this vulnerability in their inventory and assess the exposure of their systems.

Why it matters

The use-after-free vulnerability in Oj::Doc iterators poses a risk to systems using the affected versions of the oj gem, requiring defenders to verify exposure and prioritize remediation efforts.

• Potential for arbitrary code execution or denial of service due to use-after-free vulnerability
• Need for verification of affected versions in inventory
• Priority for updating to fixed version 3.17.3 or later

Technical summary

The Oj::Doc iterators (each_value, each_child, each_leaf) 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. This vulnerability can lead to potential arbitrary code execution or denial of service. The issue is fixed in version 3.17.3 or later. Defenders should prioritize verifying the presence of the vulnerability in their inventory and assessing the exposure of their systems.

Defensive priority

Defenders should prioritize verifying the presence of the vulnerability in their inventory and assessing the exposure of their systems, especially those using the affected versions of the oj gem.

Recommended defensive actions

• Verify the presence of the vulnerability in your inventory
• Assess the exposure of your systems, especially those using the affected versions of the oj gem
• Update to version 3.17.3 or later if possible
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is confirmed to exist in all versions of the oj gem with ext/oj/fast.c, including version 3.17.1. The issue is fixed in version 3.17.3. Defenders should verify the presence of this vulnerability in their inventory and assess the exposure of their systems. The CVE record was published on 2026-06-19T19:36:50.000Z and has not been modified since then. The vulnerability poses a risk to systems using the affected versions of the oj gem.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.