GitHub Enterprise Server up to 3.20.1 API Endpoint allocation of resources

Summaryinfo

A vulnerability described as problematic has been identified in GitHub Enterprise Server up to 3.16.17/3.17.14/3.18.8/3.19.5/3.20.1. This affects an unknown part of the component API Endpoint. The manipulation results in allocation of resources. This vulnerability was named CVE-2026-7541. The attack may be performed from remote. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in GitHub Enterprise Server up to 3.16.17/3.17.14/3.18.8/3.19.5/3.20.1. It has been classified as problematic. Affected is an unknown code block of the component API Endpoint. The manipulation with an unknown input leads to a allocation of resources vulnerability. CWE is classifying the issue as CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. This is going to have an impact on availability. CVE summarizes:

A denial of service vulnerability was identified in GitHub Enterprise Server that allowed an unauthenticated attacker to cause service disruption by sending crafted requests with deeply nested JSON payloads to an unauthenticated API endpoint. The endpoint parsed user-controlled JSON request bodies without size or depth limits, causing excessive CPU and memory consumption. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.21 and was fixed in versions 3.20.2, 3.19.6, 3.18.9, 3.17.15, and 3.16.18. This vulnerability was reported via the GitHub Bug Bounty program.

The weakness was presented by Nguyen Nhat Anh. The advisory is shared for download at docs.github.com. This vulnerability is traded as CVE-2026-7541 since 04/30/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1499.

Upgrading eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-1432). VulDB is the best source for vulnerability data and more expert information about this specific topic.

Affected

• Microsoft GitHub Enterprise

Productinfo

Type

• Bug Tracking Software

Vendor

• GitHub

Name

• Enterprise Server

Version

• 3.16.0
• 3.16.1
• 3.16.2
• 3.16.3
• 3.16.4
• 3.16.5
• 3.16.6
• 3.16.7
• 3.16.8
• 3.16.9
• 3.16.10
• 3.16.11
• 3.16.12
• 3.16.13
• 3.16.14
• 3.16.15
• 3.16.16
• 3.16.17
• 3.17.0
• 3.17.1
• 3.17.2
• 3.17.3
• 3.17.4
• 3.17.5
• 3.17.6
• 3.17.7
• 3.17.8
• 3.17.9
• 3.17.10
• 3.17.11
• 3.17.12
• 3.17.13
• 3.17.14
• 3.18.0
• 3.18.1
• 3.18.2
• 3.18.3
• 3.18.4
• 3.18.5
• 3.18.6
• 3.18.7
• 3.18.8
• 3.19.0
• 3.19.1
• 3.19.2
• 3.19.3
• 3.19.4
• 3.19.5
• 3.20.0
• 3.20.1

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion