GitHub Enterprise Server up to 3.21.2 Configuration File configuration file resource consumption

Summaryinfo

A vulnerability classified as critical was found in GitHub Enterprise Server up to 3.17.17/3.18.11/3.19.8/3.20.4/3.21.2. This issue affects some unknown processing of the file configuration file of the component Configuration File. Executing a manipulation can lead to resource consumption. The identification of this vulnerability is CVE-2026-15007. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in GitHub Enterprise Server up to 3.17.17/3.18.11/3.19.8/3.20.4/3.21.2. It has been declared as critical. This vulnerability affects an unknown function of the file configuration file of the component Configuration File. The manipulation with an unknown input leads to a resource consumption vulnerability. The CWE definition for the vulnerability is CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. As an impact it is known to affect availability. CVE summarizes:

A denial of service vulnerability was identified in GitHub Enterprise Server that allowed an authenticated user to cause service disruption by supplying a repository release notes configuration file containing deeply nested YAML. When release notes were generated, the configuration file was parsed without a nesting depth limit, causing excessive resource consumption that could render the instance unresponsive. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.22 and was fixed in versions 3.17.18, 3.18.12, 3.19.9, 3.20.5, and 3.21.3. This vulnerability was reported via the GitHub Bug Bounty program.

The advisory is available at docs.github.com. This vulnerability was named CVE-2026-15007 since 07/07/2026. The exploitation appears to be easy. The attack can be initiated remotely. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1499 by the MITRE ATT&CK project.

Upgrading to version 3.17.18, 3.18.12, 3.19.9, 3.20.5 or 3.21.3 eliminates this vulnerability.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Bug Tracking Software

Vendor

• GitHub

Name

• Enterprise Server

Version

• 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.17.15
• 3.17.16
• 3.17.17
• 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.18.9
• 3.18.10
• 3.18.11
• 3.19.0
• 3.19.1
• 3.19.2
• 3.19.3
• 3.19.4
• 3.19.5
• 3.19.6
• 3.19.7
• 3.19.8
• 3.20.0
• 3.20.1
• 3.20.2
• 3.20.3
• 3.20.4
• 3.21.0
• 3.21.1
• 3.21.2

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion