CVE-2026-91923

HIGHPre-NVD 7.77.7—
EchelonGraph scoreHIGH confidence

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

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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

KubeSphere through 4.1.3 contains a server-side request forgery vulnerability in the git credential verification endpoint that accepts unvalidated caller-supplied URLs without allowlist restrictions. Authenticated attackers can supply arbitrary URLs to reach internal services and exfiltrate basic-auth credentials from Secrets in any namespace by leveraging the endpoint's error response handling.

CVSS v3
7.7
EG Score
7.7(high)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

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
Severity77% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 18, 2026

Advisory Details (6)

Auto-updated Sep 15, 2026
No patch confirmed yet.
generic

KubeSphere through 4.1.3 SSRF via git credential verification endpoint | Advisories | VulnCheck

https://www.vulncheck.com/advisories/kubesphere-through-4.1.3-ssrf-via-git-credential-verification-endpoint
generic

kubesphere/config/ks-core/templates/globalroles.yaml at 3ef3a6bc98b790480577e87fbc75bee5b3438862 · kubesphere/kubesphere · GitHub

https://github.com/kubesphere/kubesphere/blob/3ef3a6bc98b790480577e87fbc75bee5b3438862/config/ks-core/templates/globalroles.yaml
generic

kubesphere/pkg/kapis/resources/v1alpha2/handler.go at 3ef3a6bc98b790480577e87fbc75bee5b3438862 · kubesphere/kubesphere · GitHub

https://github.com/kubesphere/kubesphere/blob/3ef3a6bc98b790480577e87fbc75bee5b3438862/pkg/kapis/resources/v1alpha2/handler.go
generic

kubesphere/pkg/models/git/git.go at 3ef3a6bc98b790480577e87fbc75bee5b3438862 · kubesphere/kubesphere · GitHub

https://github.com/kubesphere/kubesphere/blob/3ef3a6bc98b790480577e87fbc75bee5b3438862/pkg/models/git/git.go
generic

GitHub - kubesphere/kubesphere: The container platform tailored for Kubernetes multi-cloud, datacenter, and edge management ⎈ 🖥 ☁️ · GitHub

https://github.com/kubesphere/kubesphere
generic

Authenticated SSRF with response body exfiltration via git credential verification endpoint · Issue #6653 · kubesphere/kubesphere · GitHub

https://github.com/kubesphere/kubesphere/issues/6653

Vendor Advisories for CVE-2026-91923(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 28× in last 7d / 28× 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-09-21 07:25 UTCEG score recompute
  2. 2026-09-21 07:25 UTCGHSA enrichment
  3. 2026-09-20 20:16 UTCEPSS rescore
  4. 2026-09-20 19:16 UTCGHSA enrichment
  5. 2026-09-20 07:07 UTCGHSA enrichment
  6. 2026-09-19 18:58 UTCEG score recompute
  7. 2026-09-19 18:58 UTCGHSA enrichment
  8. 2026-09-19 06:49 UTCEG score recompute
  9. 2026-09-19 06:49 UTCGHSA enrichment
  10. 2026-09-18 19:28 UTCEPSS rescore
  11. 2026-09-18 18:33 UTCEG score recompute
  12. 2026-09-18 18:33 UTCGHSA enrichment
  13. 2026-09-18 17:29 UTCEG score recompute
  14. 2026-09-18 17:29 UTCGHSA enrichment
  15. 2026-09-18 12:23 UTCGHSA enrichment
  16. 2026-09-18 00:14 UTCEG score recompute
  17. 2026-09-18 00:14 UTCGHSA enrichment
  18. 2026-09-17 19:32 UTCEPSS rescore
  19. 2026-09-17 12:05 UTCGHSA enrichment
  20. 2026-09-16 23:56 UTCEG score recompute
  21. 2026-09-16 23:56 UTCGHSA enrichment
  22. 2026-09-16 14:09 UTCEPSS rescore
  23. 2026-09-16 11:47 UTCGHSA enrichment
  24. 2026-09-15 23:38 UTCEG score recompute
  25. 2026-09-15 23:38 UTCGHSA enrichment
Show 3 more
  1. 2026-09-15 11:29 UTCEG score recompute
  2. 2026-09-15 11:03 UTCEG score recompute
  3. 2026-09-15 11:02 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-91923?
CVE-2026-91923 is a high vulnerability published on September 15, 2026. KubeSphere through 4.1.3 contains a server-side request forgery vulnerability in the git credential verification endpoint that accepts unvalidated caller-supplied URLs without allowlist restrictions. Authenticated attackers can supply arbitrary URLs to reach internal services and exfiltrate…
When was CVE-2026-91923 disclosed?
CVE-2026-91923 was first published in the National Vulnerability Database on September 15, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-91923 actively exploited?
CVE-2026-91923 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.7% of all scored CVEs.
What is the CVSS score of CVE-2026-91923?
CVE-2026-91923 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-91923?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-91923, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-91923?

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

Start Free Scan →Browse All CVEs