CVE-2026-15007: Denial of service vulnerability in GitHub Enterprise Server allowed service disruption via deeply nested YAML in release notes configuration
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.17.18 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.18.12 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.19.9 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.20.5 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.21.3
Event History
Frequently Asked Questions
What is the severity of CVE-2026-15007?
The severity of CVE-2026-15007 is rated as medium with a CVSS score of 5.7.
How does CVE-2026-15007 affect GitHub Enterprise Server?
CVE-2026-15007 allows an authenticated user to disrupt service by using a deeply nested YAML in the release notes configuration.
Who can exploit the CVE-2026-15007 vulnerability?
Only authenticated users can exploit the CVE-2026-15007 vulnerability in GitHub Enterprise Server.
What are the consequences of the CVE-2026-15007 vulnerability?
The consequence of CVE-2026-15007 is a denial of service, leading to potential service disruptions within GitHub Enterprise Server.
How can I mitigate the risk of CVE-2026-15007?
To mitigate the risk of CVE-2026-15007, ensure that release notes configuration files do not contain deeply nested YAML.