CVE-2026-84196
Authenticated SSRF in Kyverno apiCall.service.url enabling internal HTTP requests and data leakage
Is CVE-2026-84196 being exploited?
Not confirmed. CVE-2026-84196 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.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-84196?
CVE-2026-84196 is rated High. 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-84196?
Yes. A fix has been recorded for CVE-2026-84196. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-84196 affect?
CVE-2026-84196 affects Kyverno < 1.18.0, Kubernetes clusters using Kyverno, Internal services and cloud metadata endpoints (AWS/GCP/Azure). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-84196?
Upgrade Kyverno to >=1.18.0 and restrict apiCall/RBAC; block metadata access where possible
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated SSRF allows attacker-controlled HTTP requests to internal services, loopback and cloud metadata; responses reflected in admission errors enabling data exfiltration.
Immediate action required
- affected< 1.18.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.