Skip to content
Cloud

CVE-2026-84200

9.4
Critical
EPSS 0.18%Patch availableSep 1, 2026

Kyverno policy-exception bug allows enforce-mode policy bypass enabling dangerous host mounts.

common questions

Is CVE-2026-84200 being exploited?

Not confirmed. CVE-2026-84200 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.18% probability of exploitation in the next 30 days.

How severe is CVE-2026-84200?

CVE-2026-84200 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-84200?

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

What does CVE-2026-84200 affect?

CVE-2026-84200 affects Kyverno v1.9.0 - v1.12.7, Kubernetes clusters using Kyverno policy engine. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-84200?

Upgrade Kyverno to v1.13.0+, audit hostPath policies, and block risky exceptions.

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

executive summary
technical analysis
affected
Kyverno v1.9.0 - v1.12.7Kubernetes clusters using Kyverno policy engine
impact

Attackers can craft resource names to bypass enforce-mode policies (e.g., allow hostPath mounts), enabling container-to-host compromise and potential RCE.

action required

Immediate action required

affected versions
kyverno kyverno
  • affected< 1.13.0
vendor says fixed in1.13.0

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.

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
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free