CVE-2026-100705

HIGHPre-NVD 7.67.6—
EchelonGraph scoreHIGH confidence

Score 7.6 from GitHub Security Advisory (severity: HIGH) published 2026-09-26. A secondary CVSS source baseline 7.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.6
EG Score
7.6HIGHhigh confidence
EG Risk
34
EG Risk 34/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity76% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 26, 2026

Last Modified

September 28, 2026

Advisory Details (2)

Auto-updated Sep 26, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Kyverno before 1.19.1 SSRF via legacy apiCall service executor | Advisories | VulnCheck

https://www.vulncheck.com/advisories/kyverno-before-1.19.1-ssrf-via-legacy-apicall-service-executor
github Patch Available🟡 PoC Available

Legacy `apiCall` service executor and GlobalContextEntry bypass the SSRF blocklist / SA-token egress controls that were applied only to the CEL http path · Advisory · kyverno/kyverno · GitHub

https://github.com/kyverno/kyverno/security/advisories/GHSA-q825-p383-r9v5

Vendor Advisories for CVE-2026-100705(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 29× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 03:09 UTCEG score recompute
  2. 2026-10-05 03:09 UTCGHSA enrichment
  3. 2026-10-04 23:21 UTCEPSS rescore
  4. 2026-10-04 16:02 UTCGHSA enrichment
  5. 2026-10-04 04:55 UTCGHSA enrichment
  6. 2026-10-03 17:48 UTCEG score recompute
  7. 2026-10-03 17:48 UTCGHSA enrichment
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-03 06:42 UTCGHSA enrichment
  10. 2026-10-02 19:35 UTCEG score recompute
  11. 2026-10-02 19:35 UTCGHSA enrichment
  12. 2026-10-02 08:28 UTCGHSA enrichment
  13. 2026-10-01 21:22 UTCEG score recompute
  14. 2026-10-01 21:22 UTCGHSA enrichment
  15. 2026-10-01 19:49 UTCEPSS rescore
  16. 2026-10-01 10:15 UTCGHSA enrichment
  17. 2026-09-30 23:09 UTCEG score recompute
  18. 2026-09-30 23:08 UTCGHSA enrichment
  19. 2026-09-30 15:02 UTCEPSS rescore
  20. 2026-09-30 11:58 UTCGHSA enrichment
  21. 2026-09-30 00:51 UTCEG score recompute
  22. 2026-09-30 00:51 UTCGHSA enrichment
  23. 2026-09-29 15:20 UTCEPSS rescore
  24. 2026-09-29 13:44 UTCGHSA enrichment
  25. 2026-09-29 02:34 UTCEG score recompute
Show 14 more
  1. 2026-09-29 02:34 UTCGHSA enrichment
  2. 2026-09-28 15:27 UTCEG score recompute
  3. 2026-09-28 15:27 UTCGHSA enrichment
  4. 2026-09-28 13:50 UTCEPSS rescore
  5. 2026-09-28 08:41 UTCGHSA enrichment
  6. 2026-09-27 21:34 UTCEG score recompute
  7. 2026-09-27 21:34 UTCGHSA enrichment
  8. 2026-09-27 10:27 UTCEG score recompute
  9. 2026-09-27 10:27 UTCGHSA enrichment
  10. 2026-09-26 23:17 UTCEG score recompute
  11. 2026-09-26 23:17 UTCGHSA enrichment
  12. 2026-09-26 14:26 UTCEG score recompute
  13. 2026-09-26 13:34 UTCEG score recompute
  14. 2026-09-26 13:30 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-100705?
CVE-2026-100705 is a high vulnerability published on September 26, 2026. 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…
When was CVE-2026-100705 disclosed?
CVE-2026-100705 was first published on September 26, 2026, with the most recent update on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100705 actively exploited?
CVE-2026-100705 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100705?
CVE-2026-100705 has a CVSS base score of 7.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100705?
A fix for CVE-2026-100705 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100705 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-100705

Explore →

Is Your Infrastructure Affected by CVE-2026-100705?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs