VulnerabilityPublished 5 Nov 2026

CVE-2026-122312: kyverno · Improper Privilege Management

Affects kyvernoSource CVE Database V5

Compare

Not known to be exploited · CVSS 8.3 High : upgrade to 1.19.2 soon.

Data as of 5 Nov 2026, 03:11 UTC

CVSS 4.0 base score

8.3High

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

Thin evidence

One scorer or none

CVSS scores by source
CNA (VulnCheck)	CVSS 4.0	8.3
CNA (VulnCheck)	CVSS 3.1	7.7

Patch: Available – fixed in 1.19.2

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: High
Subsequent system integrity: None
Subsequent system availability: None

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: High: There is a total loss of confidentiality, resulting in all resources within the Subsequent System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Nov 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 5 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 kyverno to 1.19.2.

Affected software

Product	Affected	Fixed in
kyvernokyverno	Affected >=1.19.1 <1.19.2	Fixed in 1.19.2
Gokyverno`pkg:golang/kyverno`Other threats	Affected >=1.19.1 <1.19.2	Fixed in 1.19.2

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

AI-suggested

Upgrade Kyverno to version 1.19.2 or later, where this vulnerability is fixed. The fix addresses the improper handling of the '?' character in URL paths to enforce correct namespace isolation. No other mitigation is indicated or required.

Description

CVE-2026-122312 is a high-severity vulnerability in Kyverno versions 1.19.1 up to but not including 1.19.2. It involves an improper privilege management issue where a namespace isolation bypass occurs due to incorrect handling of the '?' character in URL paths. This allows users with permission to create namespaced policies to craft URLs that bypass namespace restrictions and access cluster-scoped resources outside their namespace.

Impact

An attacker with the ability to create namespaced policies can bypass namespace isolation controls and read cluster-scoped resources that should be inaccessible, potentially exposing sensitive cluster-wide information. The vulnerability has a CVSS 4.0 score of 8.3 (high severity), indicating a significant risk due to network attack vector, low attack complexity, and no required user interaction.

Summary

Kyverno versions >=1.19.1 and <1.19.2 contain a namespace isolation bypass vulnerability in the APICall Fetch() function located in pkg/engine/apicall/apiCall.go. The root cause is that the path.Clean function treats the '?' character as part of the path, enabling the namespace regex to match segments inside the query string. Consequently, users authorized to create namespaced policies can supply a URLPath such as /api/v1/nodes?x=/namespaces/default/ that passes validation but results in client-go requesting cluster-scoped endpoints. This leads to unauthorized reading of resources outside the user's namespace.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2026, 03:11 UTC

Technical details

References

Community reviews

Related threats