High [CVE-2026-54900] Heap corruption via crafted JSON object key
This high-severity Red Hat Linux advisory covers CVE-2026-54900.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
Oj (Optimized JSON) is a JSON parser and Object marshaller packaged as a Ruby gem. In versions prior to 3.17.2, when in usual mode with create_id enabled, Oj::Parser#parse is vulnerable to heap corruption via a negative-size memcpy.
When a JSON object key is exactly 65,535 bytes long, an integer truncation in form_attr (usual.c:63) converts the length to -1 before passing it to memcpy. This causes memcpy to copy SIZE_MAX bytes (interpreted as a huge size_t), corrupting heap memory and crashing the process.
The issue has been fixed in version 3.17.2. A flaw was found in Oj, a Ruby gem for JSON parsing.
When processing a specially crafted JSON object key of a specific length (65,535 bytes) in usual mode with create_id enabled, an integer truncation vulnerability occurs. This leads to a negative size being passed to the `memcpy` function, causing heap memory corruption and crashing the process.
A remote attacker could exploit this to cause a denial of service. Red Hat's only product shipping the Oj Ruby gem (Compliance Backend) already includes version 3.17.3, which contains the fix for this vulnerability.
No Red Hat products are affected. Red Hat severity: Important — CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
Weakness: CWE-131.
- < 3.17.2
Official advisory · high-confidence parse· fetched 12 days ago·verify at source
Mitigation
Upgrade to a fixed release: 3.17.2. That is the remediation for this advisory.
The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.
Official advisory · high-confidence parse· fetched 12 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.