LiveActive security incident?Get immediate response
CVE Record

CVE-2026-84200: Kyverno before v1.13.0 Policy Bypass via Multiple Exceptions

Kyverno versions v1.9.0 through v1.12.7 contain a policy exception handling flaw. When a policy in enforce mode is combined with two PolicyExceptions, the less restrictive exception takes precedence, allowing an attacker to bypass the policy by crafting a resource name that matches the second exception's name pattern (e.g., '*ingress*'). This can be used to circumvent policies such as one blocking hostPath volumes. Fixed in v1.13.0.

CriticalCVSS 9.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Kyverno may approve Kubernetes resources that an enforce-mode policy should block when multiple policy exceptions apply. An authorized attacker could exploit the more permissive exception to bypass controls, potentially enabling dangerous configurations such as hostPath volumes. The flaw affects versions 1.9.0 through 1.12.7 and is fixed in 1.13.0.

Executive priority

Treat as an urgent remediation for affected clusters because policy enforcement is a security boundary and the stated potential impact is broad. Prioritize internet-facing, shared, or high-value clusters where low-privileged users can create workloads and multiple exceptions protect sensitive controls. Confirm exposure promptly, then upgrade through normal emergency-change procedures.

Technical view

When an enforce-mode policy matches two PolicyExceptions, affected Kyverno versions can give precedence to the less restrictive exception. A resource name matching that exception’s pattern may consequently bypass policy validation. Exploitation requires Kubernetes API access sufficient to submit the relevant resource; the CVSS 4.0 vector rates attack proximity as adjacent and privileges required as low.

Likely exposure

Exposure requires Kyverno 1.9.0–1.12.7, enforce-mode policies, and multiple applicable PolicyExceptions, particularly broad name patterns. Clusters without that combination are unlikely to reach the vulnerable path. Impact depends on which controls can be bypassed and what resource permissions potential attackers possess.

Exploitation context

The supplied sources do not establish active exploitation, and the CVE is not identified as being in KEV. The described technique abuses exception-selection behavior rather than defeating Kubernetes authentication. An attacker must already have sufficient access to create or modify a resource covered by the affected policy and exceptions.

Researcher notes

The essential precondition is simultaneous applicability of multiple PolicyExceptions to an enforce-mode policy. Investigation should map exception overlap, pattern breadth, policy sensitivity, and subjects permitted to create matching resources. The supplied example involves bypassing a hostPath-blocking policy, but evidence does not establish that every policy or exception arrangement is exploitable.

Mitigation direction

  • Upgrade Kyverno to version 1.13.0 or later.
  • Prioritize clusters using enforce-mode policies with multiple PolicyExceptions.
  • Review and narrow broad exception name patterns.
  • Remove unnecessary or overlapping PolicyExceptions until upgrading.
  • Restrict resource-creation permissions to reduce reachable attack paths.

Validation and detection

  • Inventory Kyverno versions across every Kubernetes cluster.
  • Identify enforce-mode policies associated with two or more PolicyExceptions.
  • Review exception patterns for broad or overlapping resource-name matches.
  • Confirm version 1.13.0 or later after remediation.
  • Validate critical policies safely in staging with representative permitted and denied resources.
  • Review admission and audit records for unexpectedly accepted policy violations.
Prepared
Confidence
high
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-84200 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.4 (4.0)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.4CVSS 4.0CriticalCVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——VulnCheck
9CVSS 3.1CriticalCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H2.36VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

9.4Critical
CVSS 4.0 vector shape for CVE-2026-84200Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
kyvernokyverno0, 1.13.0unaffected
Weakness

CWE details

CWE-284

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-284 · source CWE mapping

CWE mapping pending import

This CVE carries a CWE mapping that will resolve to a full Glexia CWE intelligence page after the official CWE import is complete.

Open CWE intelligenceSame-CWE CVEs