cve.bz

CVE-2026-0573 github enterprise server: Open Redirect

7.6 highEPSS 0.7%Fix available

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

On this page
An URL redirection vulnerability was identified in GitHub Enterprise Server that allowed attacker-controlled redirects to leak sensitive authorization tokens. The repository_pages API insecurely followed HTTP redirects when fetching artifact URLs, preserving the authorization header containing a privileged JWT. An authenticated user could redirect these requests to an attacker-controlled domain, exfiltrate the Actions.ManageOrgs JWT, and leverage it for potential remote code execution. Attackers would require access to the target GitHub Enterprise Server instance and the ability to exploit a legacy redirect to an attacker-controlled domain. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.19 and was fixed in versions 3.19.2, 3.18.4, 3.17.10, 3.16.13, 3.15.17, and 3.14.22. This vulnerability was reported via the GitHub Bug Bounty program.

Severity

CVSS 4.0

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

CVSS 3.1

9.0 critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 55th 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-02-18. 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-601 URL Redirection to Untrusted Site (Open Redirect)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

  • GitHub Enterprise Server: fixed in 3.14.22
  • GitHub Enterprise Server: fixed in 3.15.17
  • GitHub Enterprise Server: fixed in 3.16.13
  • GitHub Enterprise Server: fixed in 3.17.10
  • GitHub Enterprise Server: fixed in 3.18.4
  • GitHub Enterprise Server: fixed in 3.19.2

Ask an AI about this CVE

Show the promptExplain CVE-2026-0573 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-0573?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-0573?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-0573 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 through 3.14.21
GitHub Enterprise Serverfrom 3.15 through 3.15.16
GitHub Enterprise Serverfrom 3.16 through 3.16.12
GitHub Enterprise Serverfrom 3.17 through 3.17.9
GitHub Enterprise Serverfrom 3.18 through 3.18.3
GitHub Enterprise Serverfrom 3.19 through 3.19.1

Fixed in

ProductFixed in
GitHub Enterprise Server3.14.22
GitHub Enterprise Server3.15.17
GitHub Enterprise Server3.16.13
GitHub Enterprise Server3.17.10
GitHub Enterprise Server3.18.4
GitHub Enterprise Server3.19.2

Attack patterns (CAPEC)

  • CAPEC-178 Cross-Site Flashing Likelihood: Medium · Severity: Medium

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

References

Check your stackJSON