Improper Handling of HTTP Redirects vulnerability was identified in GitHub Enterprise Server that allowed leaking of authorization token and enabled remote code execution

Summary

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.

Timeline

1. Feb 18, 2026, 8:37 PM UTCCVE published
2. Feb 18, 2026, 9:18 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: total

3. Feb 18, 2026, 9:20 PM UTCRecord last updated

Affected versions

• GitHub Enterprise Server

  From 3.14 · through 3.14.21; From 3.15 · through 3.15.16; From 3.16 · through 3.16.12; From 3.17 · through 3.17.9; From 3.18 · through 3.18.3; From 3.19 · through 3.19.1

References 6