Kyverno has unrestricted outbound requests in Kyverno apiCall enabling SSRF

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary A Server-Side Request Forgery (SSRF) vulnerability in Kyverno allows authenticated users to induce the admission controller to send arbitrary HTTP requests to attacker-controlled endpoints. When a ClusterPolicy uses apiCall.service.url with variable substitution (e.g. {{request.object.}}), user-controlled input can influence the request target. The Kyverno admission controller executes these requests from its privileged network position without enforcing any validation or network restrictions. The issue becomes non-blind SSRF, as response data from internal services can be reflected back to the user via admission error messages. --- Details Kyverno supports variable substitution in apiCall.service.url, a documented feature intended to enable dynamic external lookups during admission control. However, the current implementation lacks fundamental safeguards in the HTTP execution path: Missing protections - No URL validation User-controlled input is directly embedded into the…

Published by the source

14 Apr 2026, 20:05 UTC

Last modified by the source

14 Apr 2026, 20:05 UTC

Source last checked

26 Oct 2026, 15:19 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-qr4g-8hrp-c4rw

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-qr4g-8hrp-c4rw

Advisory: Kyverno has unrestricted outbound requests in Kyverno apiCall enabling SSRF
IDs: GHSA-qr4g-8hrp-c4rw
Record: https://patchnext.com/advisories/ghsa-qr4g-8hrp-c4rw (revision 1, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/kyverno/kyverno: affected <= 1.17.1

## Suggested inspection (read-only)
- Go github.com/kyverno/kyverno: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/kyverno/kyverno.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-qr4g-8hrp-c4rw (GitHub-reviewed advisory GHSA-qr4g-8hrp-c4rw lists affected ranges: Go github.com/kyverno/kyverno >=0 <=1.17.1)

Commands are suggestions: review each one before running it.