cve.bz

CVE-2026-84199 kyverno kyverno: SSRF

6.9 mediumEPSS 0.4%Fix available

Medium (6.9) in kyverno kyverno. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/kyverno/kyverno 1.16.2.

On this page
Kyverno before 1.16.2 contains a server-side request forgery (SSRF) vulnerability in the APICall feature. The URL field in a Policy's ServiceCall configuration is not validated, so a user with namespace-level Policy creation permissions can direct Kyverno to make HTTP requests to arbitrary internal resources (e.g., cloud metadata endpoints such as 169.254.169.254 or other tenants' resources). Because Kyverno executes these requests using its cluster-wide high-privilege ServiceAccount (a Confused Deputy problem), the responses—potentially including other tenants' secrets and cloud IAM credentials—are returned in the PolicyReport and can be read by the attacker, breaking multi-tenant isolation.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L

CVSS 3.1

7.7 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 30th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-09-01. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • github.com/kyverno/kyverno (Go): fixed in 1.16.2

Ask an AI about this CVE

Show the promptExplain CVE-2026-84199 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-84199?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-84199?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-84199 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
kyvernobefore 1.16.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-fmqp-4wfc-w3v7Gogithub.com/kyverno/kyverno<1.16.21.16.2
GO-2026-5371Gogithub.com/kyverno/kyverno<1.16.21.16.2

Red Hat

Red Hat rates this Important.

Red Hat's statement

Important: Kyverno in Konflux is vulnerable to information disclosure via Server-Side Request Forgery. A user with namespace-level policy creation permissions can exploit an unvalidated URL in the APICall feature to access sensitive internal resources, including cloud metadata and other tenants' credentials, due to Kyverno's cluster-wide high-privilege ServiceAccount, thereby compromising multi-tenant isolation.

Red Hat's mitigation

Exploitation of this flaw requires the ability to create or modify Kyverno Policy, ClusterPolicy, or GlobalContextEntry resources. The primary mitigation is to remove policy-authoring permissions from untrusted and namespace-scoped users: restrict create, update, and patch on policies.kyverno.io, clusterpolicies.kyverno.io, and globalcontextentries.kyverno.io to cluster administrators, and audit any Role or ClusterRole that grants these verbs to tenant service accounts.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-84199.

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON