CVE-2026-15007: 
GitHub Enterprise Server Analyse et atténuation des vulnérabilités

CVE-2026-15007 is a denial-of-service (DoS) vulnerability in GitHub Enterprise Server (GHES) that allows an authenticated user to render the instance unresponsive by supplying a repository release notes configuration file containing deeply nested YAML. When release notes are generated, the YAML parser processes the configuration without enforcing a nesting depth limit, causing excessive resource consumption. The vulnerability affects all GHES versions prior to 3.22, specifically versions 3.17.0–3.17.17, 3.18.0–3.18.11, 3.19.0–3.19.8, 3.20.0–3.20.4, and 3.21.0–3.21.2. It was disclosed on July 17, 2026, and carries a CVSS v4.0 base score of 5.7 (Medium) (GitHub Advisory, GHES 3.17 Release Notes).

The root cause is classified as CWE-770 (Allocation of Resources Without Limits or Throttling), with an estimated secondary classification of CWE-400 (Uncontrolled Resource Consumption). The YAML parser used during release note generation does not impose a maximum nesting depth on the configuration file it processes, meaning a specially crafted file with arbitrarily deep YAML nesting can trigger recursive or iterative parsing that exhausts CPU and/or memory resources on the server. Exploitation requires the attacker to have write access to a repository on the GHES instance (to upload the malicious configuration file) and then trigger the release notes generation workflow. No public proof-of-concept code has been identified (GitHub Advisory, GHES 3.21 Release Notes).

Successful exploitation causes the GitHub Enterprise Server instance to become unresponsive, resulting in a complete availability impact for all users and services hosted on that instance. Because GHES is typically a central platform for source code management, CI/CD pipelines, and developer collaboration within an organization, an outage can disrupt software development workflows, block deployments, and prevent access to repositories. There is no confidentiality or integrity impact — the vulnerability is purely a denial-of-service condition (GitHub Advisory, GHES 3.18 Release Notes).

There is no public proof-of-concept exploit and no evidence of in-the-wild exploitation as of the disclosure date (GitHub Advisory). The vulnerability requires authentication and repository write access, limiting the attacker pool to trusted insiders or compromised accounts. The EPSS score is approximately 0.0027 (0.27%), indicating a low probability of exploitation in the near term. The CVE is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. NVD's SSVC assessment classifies exploitation as "none" and the attack as not automatable (Feedly).

1. Gain authenticated access: Obtain valid credentials for a GitHub Enterprise Server account with write access to at least one repository on the target instance.
2. Craft a malicious YAML file: Create a release notes configuration file (e.g., .github/release.yml) containing deeply nested YAML structures — for example, hundreds or thousands of levels of nested mappings or sequences — designed to exhaust the parser's resources.
3. Upload the configuration file: Commit and push the malicious .github/release.yml file to the target repository on the GHES instance.
4. Trigger release notes generation: Initiate the release notes generation process for the repository (e.g., via the GitHub UI or API when creating a release), causing the server to parse the malicious YAML file without a depth limit.
5. Achieve denial of service: The unbounded recursive parsing consumes excessive CPU and/or memory, rendering the GHES instance unresponsive to all users (GitHub Advisory, GHES 3.19 Release Notes).

• Logs: Server application logs showing release notes generation requests immediately preceding a service outage or high resource utilization spike; errors related to YAML parsing or memory exhaustion in GHES application logs.
• File System: Presence of a .github/release.yml file in a repository with an unusually large file size or abnormally deep YAML nesting structure.
• Process/Resource: Sudden and sustained spike in CPU or memory consumption on the GHES appliance correlated with a release notes generation event; monitoring dashboards showing the instance becoming unresponsive.
• Audit Log: GHES audit log entries showing a repository push or release creation event by an authenticated user shortly before the instance became unresponsive (GitHub Advisory).

GitHub has released patches addressing this vulnerability in GHES versions 3.17.18, 3.18.12, 3.19.9, 3.20.5, and 3.21.3, all published on July 16, 2026. Administrators should upgrade to one of these patched versions as the primary remediation. As a compensating control prior to patching, administrators can restrict repository write access to trusted users only, limiting who can upload release notes configuration files. Additionally, monitoring for unusual resource consumption spikes during release note generation can help detect exploitation attempts (GHES 3.17 Release Notes, GHES 3.21 Release Notes, GitHub Advisory).

The vulnerability was reported through the GitHub Bug Bounty program and disclosed alongside several other GHES security fixes in the July 16, 2026 patch releases. No notable independent researcher commentary, social media discussion, or significant media coverage specific to CVE-2026-15007 has been identified, consistent with its medium severity rating and lack of public exploit code (GitHub Advisory).