Skip to content
Heist/ feed
Back to feed
High

Kyverno before 1.19.1 SSRF via legacy apiCall service executor

Type: advisorySources: OSV

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.

Products
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2026-100705
Confirmed fixed CVEs
Not specified
Updated in this feed
4 Nov 2026, 15:45 UTC · Revision 1

Source evidence

Kyverno before 1.19.1 SSRF via legacy apiCall service executor

core-osv · Original source

Published 26 Sept 2026, 13:23 UTC

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.

osv:CVE-2026-100705
Complete source record
{
  "id": "9c48e70683a71faa4df650f4f70eb851ab7435eb9df416e964fb2974e94c90f3",
  "url": "https://osv.dev/vulnerability/CVE-2026-100705",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Kyverno before 1.19.1 SSRF via legacy apiCall service executor",
    "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.",
    "evidence": "osv:CVE-2026-100705",
    "products": [],
    "severity": "high",
    "structured": {
      "id": "CVE-2026-100705",
      "aliases": [
        "BIT-kyverno-2026-100705",
        "CVE-2026-100705",
        "GHSA-q825-p383-r9v5"
      ],
      "metrics": [
        {
          "type": "CVSS_V4",
          "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/kyverno/kyverno",
              "type": "GIT",
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "40ec788d48bb28d83dbf85538e962a59db9d45c6"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "range": [
                      {
                        "introduced": "0"
                      },
                      {
                        "fixed": "1.19.1"
                      }
                    ],
                    "source": "AFFECTED_FIELD",
                    "strategy": "StandardRange"
                  },
                  {
                    "range": [
                      {
                        "introduced": "0"
                      },
                      {
                        "fixed": "1.19.1"
                      }
                    ],
                    "source": "DESCRIPTION"
                  }
                ]
              }
            }
          ],
          "versions": [
            "v1.19.1-rc.1",
            "v1.19.0",
            "kyverno-policies-chart-3.9.0",
            "kyverno-chart-3.9.0",
            "v1.19.0-rc.4",
            "kyverno-policies-chart-3.9.0-rc.4",
            "kyverno-chart-3.9.0-rc.4",
            "v1.19.0-rc.3",
            "kyverno-policies-chart-3.9.0-rc.3",
            "kyverno-chart-3.9.0-rc.3",
            "v1.19.0-rc.2",
            "kyverno-policies-chart-3.9.0-rc.2",
            "kyverno-chart-3.9.0-rc.2",
            "v1.19.0-rc.1",
            "kyverno-policies-chart-3.9.0-rc.1",
            "kyverno-chart-3.9.0-rc.1",
            "1.9-dev",
            "1.8-dev",
            "1.7-dev",
            "test-dev",
            "1.6-dev",
            "helm-chart-v2.1.3",
            "v1.5.0-rc1",
            "helm-chart-v2.1.0",
            "v1.4.3",
            "helm-chart-v2.0.3",
            "v1.4.3-rc2",
            "helm-chart-v2.0.3-rc2",
            "v1.4.3-rc1",
            "helm-chart-v2.0.3-rc1",
            "v1.4.2",
            "v1.4.2-rc4",
            "v1.4.2-rc3",
            "v1.4.2-rc2",
            "v1.4.2-rc1",
            "v1.4.1",
            "v1.4.0-rc4",
            "v1.4.0",
            "v1.4.0-rc3",
            "v1.4.0-rc2",
            "v1.4.0-rc1",
            "v1.3.6",
            "v1.3.6-rc5",
            "v1.3.6-rc4",
            "v1.3.6-rc3",
            "v1.3.6-rc2",
            "v1.3.6-rc1",
            "v1.3.5",
            "v1.3.5-rc5",
            "v1.3.5-rc4",
            "v1.3.5-rc3",
            "v1.3.5-rc2",
            "v1.3.5-rc1",
            "v1.3.4",
            "v1.3.4-rc1",
            "v1.3.3",
            "v1.3.2",
            "v1.3.2-rc3",
            "v1.3.2-rc2",
            "v1.3.2-rc1",
            "v1.3.1",
            "v1.3.0",
            "v1.3.0-rc12",
            "v1.3.0-rc11",
            "v1.3.0-rc10",
            "1.3.0-rc10",
            "v1.3.0-rc9",
            "v1.3.0-rc8",
            "v1.3.0-rc7",
            "v1.3.0-rc6",
            "v1.3.0-rc5",
            "v1.3.0-rc4",
            "v1.3.0-rc3",
            "v1.3.0-rc2",
            "v1.3.0-rc1",
            "v1.2.1",
            "v1.2.0",
            "v1.1.12",
            "v1.1.11",
            "v1.1.10",
            "v1.1.9",
            "v1.1.8",
            "v1.1.7",
            "v1.1.7-rc4",
            "v1.1.7-rc3",
            "v1.1.7-rc2",
            "v1.1.7-rc1",
            "v1.1.6",
            "v1.1.6-rc5",
            "v1.1.6-rc4",
            "v1.1.6-rc3",
            "v1.1.6-rc2",
            "v1.1.6-rc1",
            "v1.1.5",
            "v1.1.4",
            "v1.1.4-rc1",
            "v1.1.3",
            "v1.1.3-rc1",
            "v1.1.2",
            "v1.1.1",
            "v1.0.0",
            "v1.0.0-rc1",
            "v0.11.0",
            "v0.10.0",
            "v0.9.1",
            "v0.9.0",
            "v0.8.0",
            "v0.7.1",
            "v0.7.0",
            "v0.5.0",
            "v0.4.0",
            "v0.3.0",
            "v0.2.0",
            "v0.1.0"
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-100705.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:37.135566568Z",
      "provider": "osv",
      "references": [
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/100xxx/CVE-2026-100705.json",
        "https://github.com/kyverno/kyverno/security/advisories/GHSA-q825-p383-r9v5",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-100705",
        "https://www.vulncheck.com/advisories/kyverno-before-1.19.1-ssrf-via-legacy-apicall-service-executor"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-918"
        ],
        "cna_assigner": "VulnCheck",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/100xxx/CVE-2026-100705.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-100705",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 504231,
  "published_at": "2026-09-26T13:23:59.999+00:00"
}