Red Hat Security Advisory: OpenShift Virtualization v4.22 Images
Affects Red HatSource GCVE Database
Not known to be exploited · CVSS 7.5 High · fixed in Red Hat package updates : patch Red Hat soon.
Data as of 3 Nov 2026, 04:44 UTC
- Patch
- Available – fixed in 5.4.1, 4.3.2, 3.15.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.
What to do
Upgrade js-yaml to 5.4.1, 4.3.2 or 3.15.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nodecajs-yaml | Affected
| Fixed in
|
| nodecajs-yaml | Affected
| Fixed in
|
| nodecajs-yaml | Affected
| Fixed in
|
AI-suggested
Red Hat has released updated OpenShift Virtualization v4.22 images that include fixes and enhancements. Users should ensure all previously released errata are applied before updating to the latest images. The vendor advisory does not specify additional mitigations or workarounds. Patch status is not explicitly confirmed in the advisory; users should apply the updated images as recommended by Red Hat. For detailed update instructions, refer to Red Hat's official documentation at https://access.redhat.com/articles/11258.
Description
CVE-2026-84375 is a denial of service vulnerability in the js-yaml JavaScript YAML parser used in Red Hat OpenShift Virtualization v4.22 images. The flaw allows an attacker to craft a specially designed YAML document that triggers excessive CPU consumption due to inefficient processing of merge keys with empty sources. This can cause prolonged CPU usage and potentially exhaust system resources when parsing untrusted YAML input.