Kyverno 1.19.1 before 1.19.2 Privilege Escalation via Policy apiCall urlPath
Kyverno 1.19.1 before 1.19.2 is affected when a namespace-scoped user can create a Policy that uses context.apiCall urlPath. 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. Kyverno version 1.19.1 up to but not including 1.19.2 Attacker is a namespace-scoped user who can create a Policy
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.36% · 29th 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? →
- 17/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, from 1.19.1 before 1.19.2 can be abused to escalate privileges to cluster admin. An attacker reaches it over the network with low-privilege login, such as a namespace-scoped user who can create a Policy, by hiding path traversal sequences behind a fragment or query so Kyverno's ServiceAccount reaches cluster-scoped endpoints.
Read the original description
Kyverno from 1.19.1 before 1.19.2 validates a Policy's context.apiCall urlPath after cleaning it but executes the raw path, whose fragment or query the Kubernetes client discards. A namespace-scoped user who can create a Policy can hide ../ segments behind # or ? to reach cluster-scoped endpoints with Kyverno's ServiceAccount, gaining cluster admin.
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
- Severity9.4/10CVSS 9.4
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Kyverno version 1.19.1 up to but not including 1.19.2 Attacker is a namespace-scoped user who can create a PolicyUpgrade to a fixed version: 1.19.2.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- kyverno kyverno
From 1.19.1 · fixed in 1.19.2
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-122310
Is CVE-2026-122310 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?
The bug is in how Kyverno validates the urlPath of a Policy's context.apiCall. A namespace-scoped user who can create a Policy can use it to reach cluster-scoped endpoints with Kyverno's ServiceAccount, which gains cluster admin.Source: vulncheck.com
Which versions are affected by CVE-2026-122310?
kyverno: from 1.19.1 before 1.19.2.Source: cve.now feed data
Am I affected, and how do I check?
Kyverno versions from 1.19.1 up to but not including 1.19.2 are in the affected range. The setup condition is a Policy that uses context.apiCall urlPath, and the attacker must be able to create a Policy in a namespace.Source: vulncheck.com
How do I fix CVE-2026-122310?
Upgrade Kyverno to 1.19.2, which is the version the advisory lists as the fix.Source: vulncheck.com