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.
CVE-2026-0573
Score 9.0 from GitHub Security Advisory (severity: HIGH) published 2026-02-18. NVD baseline CVSS 9.0; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.0
- EG Score
- 9.0(medium)
- EG Risk
- 45(Track)EG Risk 45/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 47%
- KEV
- Not listed
Published
February 18, 2026
Last Modified
June 17, 2026
Advisory Details (6)
Auto-updated Jul 28, 2026Release notes - GitHub Enterprise Server 3.19 Docs
https://docs.github.com/en/[email protected]/admin/release-notes#3.19.2Release notes - GitHub Enterprise Server 3.18 Docs
https://docs.github.com/en/[email protected]/admin/release-notes#3.18.4Release notes - GitHub Enterprise Server 3.17 Docs
https://docs.github.com/en/[email protected]/admin/release-notes#3.17.10Release notes - GitHub Enterprise Server 3.16 Docs
https://docs.github.com/en/[email protected]/admin/release-notes#3.16.13Release notes - GitHub Enterprise Server 3.15 Docs
https://docs.github.com/en/[email protected]/admin/release-notes#3.15.17Release notes - GitHub Enterprise Server 3.14 Docs
https://docs.github.com/en/[email protected]/admin/release-notes#3.14.22Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 13:27 UTCEG score recompute
- 2026-07-27 13:27 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-0573?
When was CVE-2026-0573 disclosed?
Is CVE-2026-0573 actively exploited?
What is the CVSS score of CVE-2026-0573?
How do I remediate CVE-2026-0573?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-0573
Is Your Infrastructure Affected by CVE-2026-0573?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.