CVE-2026-56852VulnerabilityPublished 10 Nov 2026Updated 13 Nov 2026

Red Hat Security Advisory: OpenShift Security Profiles Operator bug fix and enhancement update

Affects Red Hat OpenShiftSource GCVE Database

Compare

Mentioned vulnerabilities

CVE-2026-116591

Authoritative record:CVE-2026-56852· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade Red Hat norm to 0.39.0 soon.

Data as of 13 Nov 2026, 14:34 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 0.39.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Jul 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 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade golang.org/x/text/unicode/norm to 0.39.0.

Affected software

Product	Affected	Fixed in
golang.org/x/textgolang.org/x/text/unicode/norm	Affected <0.39.0	Fixed in 0.39.0
Gogolang.org/x/text/unicode/norm`pkg:golang/golang.org/x/text/unicode/norm`Other threats	Affected <0.39.0	Fixed in 0.39.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the OpenShift Security Profiles Operator v1.0.1 update which includes the fix for this vulnerability. Ensure all previously released errata relevant to your system are applied before updating. Until patched, mitigate risk by rejecting or filtering untrusted Zstandard compressed payloads at ingress proxies or restricting decompression endpoints to authenticated, trusted clients. There is no direct configuration-level workaround within the library itself. The vendor manages remediation for this product via the updated operator image.

Description

A vulnerability exists in the OpenShift Security Profiles Operator related to the klauspost compress library's Zstandard (zstd) decompression implementation. A specially crafted zstd compressed stream can cause an out-of-bounds read due to an integer handling error, leading to an unhandled panic and denial of service (DoS) by crashing the application. The issue affects applications decompressing untrusted inputs using klauspost/compress. The OpenShift Security Profiles Operator v1.0.1 update addresses this and other bugs.

Impact

The vulnerability allows a remote attacker to cause a denial of service by crashing applications that decompress untrusted Zstandard compressed streams using the vulnerable klauspost compress library. The crash occurs due to an out-of-bounds read caused by integer wraparound in the decompression logic. The impact is limited to denial of service; confidentiality and integrity are not affected. Container boundaries and non-root execution help isolate the impact from the underlying host system.

CWE-835Loop with Unreachable Exit Condition (Infinite Loop) (opens in a new tab)
Base weakness
The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.
CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Nov 2026, 14:34 UTC

Public exploits and detectionGitHub proofs of concept

WeaknessesCWE-835, CWE-125

Technical details

References

Community reviews

Related threats