Is this vulnerability remotely exploitable across the internet?

It can be exploited remotely in the sense that an attacker can interact with the GitHub Enterprise Server instance over the network, but they must already be an authenticated user and able to participate in workflows involving scoped ghu_ tokens and installations.

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

The attacker needs valid credentials to the GitHub Enterprise Server environment and the ability to trigger or take advantage of installation revocation and token flows. They do not need direct administrative access to the server, but they do need sufficient access to obtain or leverage a victim-scoped token in the affected context.

What is the safest general fix pattern for this type of vulnerability?

The most robust fix is to make authorization strictly context-bound and fail-closed: any token whose installation is revoked, deleted, or cannot be resolved must be treated as invalid, with no fallback to broader or global access. Every authorization decision must confirm that the token's scope, installation, and target repository set match the requested operation exactly.

Severity:

CRITICAL RISK

(9.6)

Improper Authorization Scope Handling (CWE-639) in GitHub Enterprise Server ghu_ Tokens

CVE-2026-5845

Published:

Apr 21, 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-284;CWE-434

HIGH RISK

HIGH

(7.3)

Unrestricted File Upload (CWE-434) via Engine Handler exec in MindsDB BYOM Integration

Remote Code Execution and Arbitrary File Upload

May 3, 2026

CWE-287

HIGH RISK

HIGH

(7.3)

Improper Authentication (CWE-287) in JwtAuthenticationTokenFilter of yudao-cloud Ruoyi-Vue-Pro

Authentication Bypass / Unauthorized Access

May 3, 2026

Vulnerability Type

Category:

Improper Authorization / Broken Access Control

CWE:

CWE-639

Impact:

Unauthorized Access to Private Repositories and Write Operations

Severity:

CRITICAL RISK

(9.6)

CVSS Version:

3.1

Vulnerability Type

Category:

Improper Authorization / Broken Access Control

CWE:

CWE-639

Impact:

Unauthorized Access to Private Repositories and Write Operations

Severity:

CRITICAL RISK

(9.6)

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

Improper Authorization Scope Handling (CWE-639) in GitHub Enterprise Server ghu_ Tokens

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)

Unrestricted File Upload (CWE-434) via Engine Handler exec in MindsDB BYOM Integration

HIGH RISK

HIGH

(7.3)

Improper Authentication (CWE-287) in JwtAuthenticationTokenFilter of yudao-cloud Ruoyi-Vue-Pro

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