High SSRF

CVE-2026-84199 — Kyverno before 1.16.2 SSRF via APICall Feature

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.

Published Sep 1, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulnCheck

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.4% (30-day exploitation probability)+4
Technical severity (high)+6
CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.36%

ahead of 28% of scored CVEs · Oct 15, 2026

Affects

Kyverno

CVSS base

7.7

High · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

Proof of concept

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Kyverno Kyverno).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (ssrf), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Kyverno	Kyverno	< 1.16.2	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

Low

User interaction

None

Scope

Changed

Confidentiality

High

Integrity

None

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
6.9	CVSS 4.0	Medium	—	—	disclosure@vulncheck.com via NIST National Vulnerability Database
6.9	CVSS 4.0	Medium	—	—	VulnCheck via CVE Program (cve.org) e CISA ADP
7.7	CVSS 3.1	High	3.1	4.0	disclosure@vulncheck.com via NIST National Vulnerability Database
7.7	CVSS 3.1	High	—	—	VulnCheck via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-918 · Server-Side Request Forgery (SSRF)

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.36%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Monitor outbound requests from the server to internal IPs and cloud metadata endpoints.

web/proxy/WAF logsnetwork IDS/IPSegress traffic

Timeline

What happened to this CVE, newest first.

2026
Affected products added · kyverno/kyverno
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 7.7
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Awaiting Analysis
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Sep 1, 2026 · VulnCheck

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

2 on the record

www.vulncheck.com/advisories/kyverno-before-1.16.2-ssrf-via-apicall-feature
third-party-advisory, NIST National Vulnerability Database
github.com/kyverno/kyverno/security/advisories/GHSA-fmqp-4wfc-w3v7
vendor-advisory, NIST National Vulnerability Database

Elsewhere on this site

Kyverno
every CVE for this vendor

SSRF
same class

CWE-918
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-100707 Kyverno before 1.19.1 Namespace Isolation Bypass via Percent-Encoded Path 20d
High CVE-2026-100703 Kyverno before 1.19.1 Cross-Namespace Data Access via globalcontext.Lib 20d
High CVE-2026-100705 Kyverno before 1.19.1 SSRF via legacy apiCall service executor 20d
Critical CVE-2026-100706 kyverno before 1.19.1 Privilege Escalation via Policy apiCall urlPath 20d
High CVE-2026-100704 Kyverno before 1.19.1 ImageValidatingPolicy Exception Bypass 20d
High CVE-2026-84195 Kyverno before 1.16.4 Credential Leak via apiCall Sep 1, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-84199 is "Kyverno before 1.16.2 SSRF via APICall Feature", rated High. It affects Kyverno (Kyverno); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.7 describes technical severity. EPSS 0.36% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.