Enterprise ServerApplication · GitHub
CVE-2026-0573
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe repository_pages API in GitHub Enterprise Server insecurely followed HTTP redirects while preserving the authorization header containing a privileged JWT token. An authenticated attacker could redirect these requests to an attacker-controlled domain, exfiltrating the Actions.ManageOrgs JWT, which could then be leveraged for potential remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Enterprise ServerApplication
< 3.14.22>= 3.15.0, < 3.15.17>= 3.16.0, < 3.16.13>= 3.17.0, < 3.17.10>= 3.18.0, < 3.18.4>= 3.19.0, < 3.19.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify your GitHub Enterprise Server versionAccess the GitHub Enterprise Server admin console or use the management shell command 'ghe-version' to retrieve the installed version numberAffected if The installed version falls within any of these ranges: < 3.14.22, >= 3.15.0 and < 3.15.17, >= 3.16.0 and < 3.16.13, >= 3.17.0 and < 3.17.10, >= 3.18.0 and < 3.18.4, or >= 3.19.0 and < 3.19.2
-
Locate audit logs for repository_pages API activityIn the GitHub Enterprise admin settings, navigate to the Audit Log section and search for events containing 'repository_pages' or query the log files for API calls to endpoints containing 'repository_pages'Affected if Any repository_pages API calls exist in the audit logs, as these requests would have been vulnerable to redirect-based token exfiltration
-
Inspect for unauthorized external redirects from API callsReview audit logs or network traffic logs for any repository_pages API requests that resulted in HTTP redirects (3xx responses) to external domains, especially unfamiliar or attacker-controlled domainsAffected if Repository_pages API calls were redirected to external domains outside your organization's infrastructure, indicating potential token exfiltration
You are affected if your installed GitHub Enterprise Server version is within the affected ranges listed above and the repository_pages API has been accessed, as the authorization header would have been forwarded to any redirect target.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.14.223.15.173.16.13
Upgrade GitHub Enterprise Server to one of the fixed versions (3.19.2, 3.18.4, 3.17.10, 3.16.13, 3.15.17, or 3.14.22) and audit logs for signs of exploitation involving the repository_pages API and unauthorized token exfiltration.
3.19.2 (or latest 3.x stable release)
- 1. Back up your GitHub Enterprise Server instance data and configuration according to your disaster recovery plan.
- 2. Schedule a maintenance window as upgrades require downtime.
- 3. Download the appropriate upgrade package for your current version from the GitHub Enterprise Server downloads page.
- 4. Follow the standard GitHub Enterprise Server upgrade procedure documented at docs.github.com/en/enterprise-server@latest/admin/installation/updating-the-github-enterprise-server-appliance.
- 5. After upgrade, verify the instance is operational by checking administrator access and core services.
- 6. Review audit logs to confirm no exploitation occurred prior to patching.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Enterprise Server
Scoped from the published advisory
- Consultation8.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0573 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0573 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data