VulnerabilityPublished 26 Sep 2026

CVE-2026-100705: Kyverno before 1.19.1 is vulnerable to server-side request forgery

Affects kyvernoSource GCVE Database

Compare

Not known to be exploited · CVSS 7.6 High : upgrade to 1.19.1 soon.

Data as of 10 Nov 2026, 23:24 UTC

CVSS 3.1 base score

7.6High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.19.1

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-8x9j-8h3w-5cxq

What to do

Upgrade kyverno/kyverno to 1.19.1.

Affected software

Product	Affected	Fixed in
GitHubkyverno/kyverno`pkg:github/kyverno/kyverno`Other threats	Affected <1.19.1	Fixed in 1.19.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in Kyverno version 1.19.1. Users should upgrade to version 1.19.1 or later to ensure the egress blocklist and scoped-token controls are properly applied to all API call paths. No additional mitigation is required once the update is applied.

Description

Kyverno versions prior to 1.19.1 contain a server-side request forgery (SSRF) vulnerability. This issue arises because certain legacy API call paths do not enforce egress filtering or validate service URLs, allowing crafted policies or resource submitters to make Kyverno send HTTP requests to arbitrary internal or external hosts. The vulnerability can lead to unauthorized access to cloud metadata endpoints and internal services using Kyverno's network privileges. The flaw is fixed in version 1.19.1.

Impact

An attacker with the ability to create or modify ClusterPolicies, GlobalContextEntries, or resource templates can exploit this vulnerability to make Kyverno send HTTP requests to arbitrary internal or external endpoints. This can lead to unauthorized disclosure of sensitive information such as cloud instance credentials from metadata services and access to internal services within the cluster. The attached ServiceAccount token may be used in some contexts, though its scoped nature limits the potential impact. The vulnerability has a CVSS v3.1 score of 7.6 (high severity), indicating significant confidentiality impact with limited integrity impact and no availability impact.

Summary

Kyverno before version 1.19.1 is vulnerable to SSRF due to incomplete application of egress blocklists and scoped-token controls. While the new CEL http.Get/Post library enforces these protections, legacy apiCall service executors and GlobalContextEntry external-API paths use a plain net/http client without egress filtering or URL validation. This allows a ClusterPolicy or GlobalContextEntry author, or a lower-privileged resource submitter templating service URLs, to cause Kyverno to issue GET/POST requests to arbitrary hosts, including cloud metadata endpoints and internal cluster services. Additionally, Kyverno attaches its projected ServiceAccount token to these requests, although the token is audience-scoped, limiting replay value. The vulnerability is addressed in Kyverno 1.19.1.

CWE-918Server-Side Request Forgery (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Implementation · Operation
If there is a known list of applications, IP, hostname, and/or domains to which the product is allowed to communicate, then use allowlists to ensure that outgoing requests are restricted to these known entities. The allowlists could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Operation
If the product is expected to be able to connect to arbitrary IP addresses or domains, consider using a denylist that includes private network addresses, internal domain names, etc. The denylist could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Sep 2026, 04:41 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats