Kyverno 1.19.1 before 1.19.2 Namespace Isolation Bypass via APICall URLPath Query String
Affects Kyverno 1.19.1 before 1.19.2 when namespaced policies use APICall URLPath query strings, letting policy authors reach other namespaces' resources. Fixed in 1.19.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.19.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected Kyverno versions are 1.19.1 up to but not including 1.19.2.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.31% · 24th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Kyverno, a Kubernetes policy engine, is affected in a version range that is not named here. A user with low privileges who can create namespaced policies can reach it over the network, and can use it to read cluster-scoped resources outside their own namespace.
Read the original description
Kyverno from 1.19.1 before 1.19.2 contains a namespace isolation bypass in APICall Fetch() in pkg/engine/apicall/apiCall.go because path.Clean treats '?' as a path character, letting the namespace regex match segments inside the query string. Users who can create namespaced policies can supply a URLPath like /api/v1/nodes?x=/namespaces/default/ that passes validation while client-go requests the cluster-scoped endpoint, reading resources outside their namespace.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected Kyverno versions are 1.19.1 up to but not including 1.19.2.Upgrade to a fixed version: 1.19.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- kyverno kyverno
From 1.19.1 · fixed in 1.19.2
Evidence 3
- Advisory
- Patch
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-122312
Is CVE-2026-122312 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A namespaced Kyverno policy that makes an APICall can bypass namespace isolation. A policy author who can create such policies can read cluster-scoped resources and resources in other namespaces, such as secrets.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-122312?
kyverno: from 1.19.1 before 1.19.2.Source: cve.now feed data
Am I affected, and how do I check?
Kyverno versions 1.19.1 up to but not including 1.19.2 are affected. To check, look at the version of the Kyverno image or release running in the cluster, for example the image tag on the Kyverno deployment.Source: vulncheck.com, github.com
How do I fix CVE-2026-122312?
Upgrade Kyverno to 1.19.2 or later, which contains the fix.Source: vulncheck.com, github.com