CVE-2026-0573: Improper Handling of HTTP Redirects vulnerability was identified in GitHub Enterprise Server that allowed leaking of authorization token and enabled remote code execution
An URL redirection vulnerability was identified in GitHub Enterprise Server that allowed attacker-controlled redirects to leak sensitive authorization tokens. The repositorypages 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-0573?
CVE-2026-0573 has been classified with a high severity due to its potential to leak sensitive authorization tokens.
How do I fix CVE-2026-0573?
To mitigate CVE-2026-0573, update your GitHub Enterprise Server to version 3.19 or later.
What systems are affected by CVE-2026-0573?
CVE-2026-0573 affects GitHub Enterprise Server versions up to but not including 3.19.
What kind of vulnerability is CVE-2026-0573?
CVE-2026-0573 is an URL redirection vulnerability that can allow unauthorized access to sensitive information.
What should I do if I cannot update to mitigate CVE-2026-0573?
If unable to update, review your configurations and restrict access to sensitive endpoints to minimize risk related to CVE-2026-0573.