Skip to content
major vulnerability· requires attention

Allows namespace user to escalate to cluster-admin via Kyverno's ServiceAccount; affects many Kubernetes clusters using Kyverno and enables full cluster compromise.

Cloud

CVE-2026-122310

9.4
Critical
EPSS 0.36%Patch available

Kyverno path validation bug lets namespace users escalate to cluster-admin.

exploited
No known exploitation not in CISA KEV as of our last sync
fix
Fixed in 1.19.2
likelihood
EPSS 0.36%top 71% of scored CVEs
Published 5 Nov 2026Analysed here 5 Nov 2026CVSS scored by the publisher (CNA)

do firstUpgrade to a fixed release: 1.19.2.

common questions

Is CVE-2026-122310 being exploited?

Not confirmed. CVE-2026-122310 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.36% probability of exploitation in the next 30 days.

How severe is CVE-2026-122310?

CVE-2026-122310 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-122310?

Yes. A fix has been recorded for CVE-2026-122310. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-122310 affect?

CVE-2026-122310 affects Kyverno 1.19.1 (prior to 1.19.2), Kubernetes clusters running Kyverno admission controller. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-122310?

Upgrade Kyverno to 1.19.2 ASAP; audit/rotate Kyverno ServiceAccount tokens.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Kyverno 1.19.1 (prior to 1.19.2)Kubernetes clusters running Kyverno admission controller
impact

Namespace-scoped user can craft a Policy that causes Kyverno to access cluster endpoints and obtain cluster-admin privileges.

action required

Immediate action required

affected versions
kyverno
  • affected>= 1.19.1 and < 1.19.2
vendor says fixed in1.19.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

timeline

  1. 5 Nov 2026Published
  2. 5 Nov 2026CVE record last updated · same day later
  3. 5 Nov 2026Analysed by vulneraibility.com · 1 day later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
2 references in the CVE record: 2 advisories
  • Advisorygithub.com /kyverno/kyverno/security/advisories/GHSA-3xfv-vq8x-qhg4
  • Advisoryvulncheck.com /advisories/kyverno-1.19.1-before-1.19.2-privilege-escalation-via-policy-apicall

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • FIRST EPSS: exploit probability and percentile
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved