CVE-2026-0573
GitHub Enterprise Server remote code execution
- Published18 Feb 2026
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:HAffected products
Remediation
References
- https://docs.github.com/en/[email protected]/admin/release-notes#3.14.22
- https://docs.github.com/en/[email protected]/admin/release-notes#3.15.17
- https://docs.github.com/en/[email protected]/admin/release-notes#3.16.13
- https://docs.github.com/en/[email protected]/admin/release-notes#3.17.10
- https://docs.github.com/en/[email protected]/admin/release-notes#3.18.4
- https://docs.github.com/en/[email protected]/admin/release-notes#3.19.2
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-0573 being actively exploited?
CVE-2026-0573 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.66%.
How severe is CVE-2026-0573?
CVE-2026-0573 has a CVSS 3.1 base score of 9.0, rated critical. EPSS estimates a 0.66% probability of exploitation.
Which products are affected by CVE-2026-0573?
Affected products include GitHub Enterprise Server.
How do I fix CVE-2026-0573?
Upgrade affected software to a fixed version, for example GitHub Enterprise Server 3.15.17 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-0573 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.