Use After Free Affecting kube-logging-operator package, versions <6.7.0-r4
Threat Intelligence
This vulnerability is trending on Twitter; this may indicate a growing threat.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CHAINGUARDLATEST-KUBELOGGINGOPERATOR-17750738
- published1 Jul 2026
- disclosed1 Jul 2026
Introduced: 1 Jul 2026
NewCVE-2026-54901 (opens in a new tab)How to fix?
Upgrade Chainguard kube-logging-operator to version 6.7.0-r4 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kube-logging-operator package and not the kube-logging-operator package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
Oj (Optimized JSON) is a JSON parser and Object marshaller packaged as a Ruby gem. In versions prior to 3.17.2, Oj::Parser in usual mode does not mark array_class and hash_class references during garbage collection, leading to Use-After-Free. If GC runs after the class is assigned but before a parse, the class object is reclaimed, leaving the parser holding a dangling VALUE. The subsequent parse call dereferences the freed object, producing a segfault. This issue has been fixed in version 3.17.2.