Kyverno before 1.19.1 contains a namespace isolation bypass in the apiCall context entry of namespaced Policy resources due to inconsistent path… (CVE-2026-100707)
Kyverno versions prior to 1.19.1 have a namespace isolation bypass vulnerability in the apiCall context entry of namespaced Policy resources. This occurs due to inconsistent path interpretation between validation and execution, allowing a low-privilege tenant to use percent-encoded dot-segments in the urlPath to bypass namespace checks. Exploitation enables reading resources from other namespaces using the Kyverno admission controller's ServiceAccount credentials.
AI Analysis
Technical Summary
Kyverno before version 1.19.1 contains a namespace isolation bypass vulnerability (CVE-2026-100707) in the apiCall context entry of namespaced Policy resources. The root cause is inconsistent path interpretation between validation and execution phases. Specifically, a low-privilege tenant can craft percent-encoded dot-segments in the urlPath to circumvent namespace checks, thereby accessing resources in other namespaces via the Kyverno admission controller's ServiceAccount credentials. This vulnerability has a CVSS 3.1 score of 7.7, indicating high severity, with network attack vector, low attack complexity, low privileges required, no user interaction, and a scope change. The impact is high confidentiality loss without integrity or availability impact.
Potential Impact
An attacker with low privileges in a Kubernetes cluster using Kyverno before 1.19.1 can bypass namespace isolation controls and read resources from other namespaces. This leads to a high confidentiality impact as sensitive data from other namespaces can be accessed. There is no reported impact on integrity or availability. The vulnerability leverages the admission controller's ServiceAccount credentials, potentially exposing cluster-wide sensitive information.
Mitigation Recommendations
A fix is available in Kyverno version 1.19.1. Users should upgrade to version 1.19.1 or later to remediate this namespace isolation bypass vulnerability. No other mitigation guidance is provided or required beyond applying the official patch.
Kyverno before 1.19.1 contains a namespace isolation bypass in the apiCall context entry of namespaced Policy resources due to inconsistent path… (CVE-2026-100707)
Description
Kyverno versions prior to 1.19.1 have a namespace isolation bypass vulnerability in the apiCall context entry of namespaced Policy resources. This occurs due to inconsistent path interpretation between validation and execution, allowing a low-privilege tenant to use percent-encoded dot-segments in the urlPath to bypass namespace checks. Exploitation enables reading resources from other namespaces using the Kyverno admission controller's ServiceAccount credentials.
CVSS v3.1
Score 7.7high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Kyverno before version 1.19.1 contains a namespace isolation bypass vulnerability (CVE-2026-100707) in the apiCall context entry of namespaced Policy resources. The root cause is inconsistent path interpretation between validation and execution phases. Specifically, a low-privilege tenant can craft percent-encoded dot-segments in the urlPath to circumvent namespace checks, thereby accessing resources in other namespaces via the Kyverno admission controller's ServiceAccount credentials. This vulnerability has a CVSS 3.1 score of 7.7, indicating high severity, with network attack vector, low attack complexity, low privileges required, no user interaction, and a scope change. The impact is high confidentiality loss without integrity or availability impact.
Potential Impact
An attacker with low privileges in a Kubernetes cluster using Kyverno before 1.19.1 can bypass namespace isolation controls and read resources from other namespaces. This leads to a high confidentiality impact as sensitive data from other namespaces can be accessed. There is no reported impact on integrity or availability. The vulnerability leverages the admission controller's ServiceAccount credentials, potentially exposing cluster-wide sensitive information.
Mitigation Recommendations
A fix is available in Kyverno version 1.19.1. Users should upgrade to version 1.19.1 or later to remediate this namespace isolation bypass vulnerability. No other mitigation guidance is provided or required beyond applying the official patch.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-66wc-m66q-pf76
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-100707"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6ab89bd9f7a7c5410694201d
Added to database: 09/27/2026, 04:30:17 UTC
Last enriched: 09/27/2026, 04:41:18 UTC
Last updated: 09/27/2026, 23:51:19 UTC
Views: 16
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.