cve.bz

CVE-2026-5921 github enterprise server: SSRF

8.9 highEPSS 0.4%Fix available

High (8.9) in github enterprise server. EPSS 0.4% 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 attacker to extract sensitive environment variables from the instance through a timing side-channel attack against the notebook rendering service. When private mode was disabled, the notebook viewer followed HTTP redirects without revalidating the destination host, enabling an unauthenticated SSRF to internal services. By chaining this with regex filter queries against an internal API and measuring response time differences, an attacker could infer secret values character by character. Exploitation required that private mode be disabled and that the attacker be able to chain the instance's open redirect endpoint through an external redirect to reach internal services. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.21 and was fixed in versions 3.14.26, 3.15.21, 3.16.17, 3.17.14, 3.18.8, 3.19.5, and 3.20.1. This vulnerability was reported via the GitHub Bug Bounty program.

Severity

CVSS 4.0

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

CVSS 3.1

8.9 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L
EPSS
0.4% (unchanged from 0.4% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 39th 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: total, assessed 2026-04-22. 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
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-5921 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-5921?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-5921?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-5921 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.14.0 before 3.14.26
GitHub Enterprise Serverfrom 3.15.0 before 3.15.21
GitHub Enterprise Serverfrom 3.16.0 before 3.16.17
GitHub Enterprise Serverfrom 3.17.0 before 3.17.14
GitHub Enterprise Serverfrom 3.18.0 before 3.18.8
GitHub Enterprise Serverfrom 3.19.0 before 3.19.5
GitHub Enterprise Serverfrom 3.20.0 before 3.20.1

Fixed in

ProductFixed in
GitHub Enterprise Server3.14.26
GitHub Enterprise Server3.15.21
GitHub Enterprise Server3.16.17
GitHub Enterprise Server3.17.14
GitHub Enterprise Server3.18.8
GitHub Enterprise Server3.19.5
GitHub Enterprise Server3.20.1

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