Is this vulnerability remotely exploitable from the public internet?

Not directly. An attacker must have authenticated access to the target GitHub Enterprise Server instance and the ability to influence or exploit redirects. However, once those conditions are met, the token exfiltration can be leveraged for high-impact actions.

What level of access does an attacker need to exploit this issue?

The attacker needs a valid account on the GitHub Enterprise Server instance and a way to cause repository_pages to follow a redirect chain that ends at an attacker-controlled domain. Direct administrative access is not required, but the resulting stolen token can grant elevated privileges.

What is the safest general fix pattern for developers and operators?

The most robust pattern is to strictly validate redirect destinations and to strip sensitive headers on any redirect to a different origin. In practice, this means using allowlists for redirect targets, disabling automatic redirect following where it is not essential, and ensuring authorization headers are applied only to clearly trusted endpoints.

Severity:

CRITICAL RISK

(9.0)

Open Redirect Token Leakage (CWE-601) in GitHub Enterprise Server repository_pages API

CVE-2026-0573

Published:

Feb 18, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

Remote Code Execution on the Router

April 6, 2026

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Remote Code Execution on Router Firmware

April 6, 2026

Vulnerability Type

Category:

Open Redirect / Token Leakage

CWE:

CWE-601

Impact:

Privilege Escalation and Potential Remote Code Execution via Token Exfiltration

Severity:

CRITICAL RISK

(9.0)

CVSS Version:

3.1

Vulnerability Type

Category:

Open Redirect / Token Leakage

CWE:

CWE-601

Impact:

Privilege Escalation and Potential Remote Code Execution via Token Exfiltration

Severity:

CRITICAL RISK

(9.0)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Open Redirect Token Leakage (CWE-601) in GitHub Enterprise Server repository_pages API

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare