Read the docs
TI-2026-64861 Aliases CVE-2026-100705GHSA-8x9j-8h3w-5cxq

Kyverno before 1.19.1 SSRF via legacy apiCall service executor

Priority LOW 35CWE-918Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
—
Confidentiality · integrity · availability
High · Low · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

Kyverno before 1.19.1 is vulnerable to server-side request forgery. The default egress blocklist (169.254.169.254, 169.254.169.253, metadata.google.internal, 127.0.0.0/8, ::1/128) and the scoped-token control were wired only into the new CEL http.Get/Post library and were never applied to the legacy apiCall service executor (pkg/engine/apicall/executor.go) or to the GlobalContextEntry external-API path, which handle every non-CEL context[].apiCall.service call. Because these paths use a plain net/http client with no egress filtering and no validation of the configured service URL, a ClusterPolicy or GlobalContextEntry author — or, where a deployed policy templates the service URL from the admission resource, a lower-privileged resource submitter — can cause Kyverno to issue GET/POST requests to an arbitrary host, including the cloud metadata endpoint, loopback, and any in-cluster service, reading cloud instance credentials and reaching internal endpoints with Kyverno's network position. The executor also unconditionally attaches Kyverno's projected ServiceAccount token to the attacker-chosen destination; the token is audience-scoped, limiting its replay value. Fixed in 1.19.1.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00197 9th percentileScored 2026-11-07
Fix Fixed kyverno (kyverno): 1.19.1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
kyvernokyvernobefore 1.19.11.19.1Patch availableCNA
  • kyverno Vendorkyverno Affected before 1.19.1 Fixed in 1.19.1 Patch available CNA

Remediation

  • Fix · CNA kyverno (kyverno) Fixed in 1.19.1

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    kyverno 1.19.1

    5 records Highest priority Priority HIGH 2 HIGH, 1 MEDIUM, 2 LOW

    Other records, highest priority first

    • TI-2026-64863 Kyverno before 1.19.1 Namespace Isolation Bypass via Percent-Encoded PathPriority HIGH 69
    • TI-2026-64860 Kyverno before 1.19.1 ImageValidatingPolicy Exception BypassPriority HIGH 69
    • TI-2026-64862 kyverno before 1.19.1 Privilege Escalation via Policy apiCall urlPathPriority MEDIUM 43
    Show all 5 records →

Vendor assessments

Red Hat

Red Hat's page for this CVE →

Not affected: 1 product
  • Red Hat

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-100705
  2. 2026-10-03 Alias added: GHSA-8x9j-8h3w-5cxq

References

Advisory 1

  • TI-2024-32618 Kyverno's PolicyException objects can be created in any namespace by default CVSS 4.0HIGH 8.7
  • TI-2026-57895 Kyverno before v1.13.0 Policy Bypass via Multiple Exceptions CVSS 4.0CRITICAL 9.4
  • TI-2026-39369 Missing authorization in kyverno CVSS 3.1CRITICAL 9.6
  • TI-2026-17733 Kyverno Cross-Namespace Privilege Escalation via Policy apiCall CVSS 3.1CRITICAL 10.0
  • TI-2026-29924 Kyverno: ServiceAccount token leaked to external servers via apiCall service URL CVSS 3.1CRITICAL 9.1
  • TI-2026-29524 kyverno apicall servicecall implicit bearer token injection leaks kyverno serviceaccount token CVSS 3.1HIGH 8.1
See all 52 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences