cve.bz

CVE-2026-18730 github enterprise server: SSRF

8.2 highEPSS 0.5%Fix available

High (8.2) in github enterprise server. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
A server-side request forgery (SSRF) vulnerability was identified in GitHub Enterprise Server that allowed an unauthenticated attacker to cause the Manage API to send crafted outbound requests to an attacker-controlled host. An unauthenticated endpoint parsed an attacker-supplied cluster configuration and issued gateway-to-agent requests whose HMAC authenticated only a timestamp, not the request path or body. An attacker positioned to intercept the outbound request could capture this token and replay it against privileged management agent endpoints. High-availability deployments were not affected due to a topology restriction. This vulnerability affected GitHub Enterprise Server releases in the 3.17, 3.18, 3.19, 3.20, and 3.21 series and was fixed in versions 3.17.21, 3.18.15, 3.19.12, 3.20.8, and 3.21.6. This vulnerability was reported via the GitHub Bug Bounty program.

Severity

CVSS 4.0

8.2 high
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

7.4 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 43rd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-09-02. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • GitHub Enterprise Server: fixed in 3.17.21
  • GitHub Enterprise Server: fixed in 3.18.15
  • GitHub Enterprise Server: fixed in 3.19.12
  • GitHub Enterprise Server: fixed in 3.20.8
  • GitHub Enterprise Server: fixed in 3.21.6

Ask an AI about this CVE

Show the promptExplain CVE-2026-18730 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-18730?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-18730?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-18730 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
GitHub Enterprise Serverfrom 3.17.0 before 3.17.*
GitHub Enterprise Serverfrom 3.18.0 before 3.18.*
GitHub Enterprise Serverfrom 3.19.0 before 3.19.*
GitHub Enterprise Serverfrom 3.20.0 before 3.20.*
GitHub Enterprise Serverfrom 3.21.0 before 3.21.*

Fixed in

ProductFixed in
GitHub Enterprise Server3.17.21
GitHub Enterprise Server3.18.15
GitHub Enterprise Server3.19.12
GitHub Enterprise Server3.20.8
GitHub Enterprise Server3.21.6

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON