Technical impact
The vulnerability is a path‑traversal flaw in GitHub Enterprise Server that occurs when Dependabot validates an incoming dependency‑file path but does not check the actual write destination. An attacker who can already execute code inside the Dependabot updater container can cause the server to write an arbitrary file to any repository location, including .github/workflows/. If a crafted dependency‑file path resolves to a workflow file and the repository permits workflows:write and executes pull_request_target or auto‑merge workflows, the injected workflow runs with the Actions runner’s privileges and can capture repository secrets, elevating local code execution to full repository compromise.
Affected Systems
All GitHub Enterprise Server releases prior to 3.23 are vulnerable unless they incorporate the complete fix. The full patch was shipped in release 3.22.3, with earlier variations of 3.19.14, 3.20.10, and 3.21.8 also fully addressing the issue. The interim fixes in 3.21.3, 3.20.5, 3.19.9, 3.18.12 and 3.17.18 were incomplete and do not remediate the flaw. Versions 3.17.x and 3.18.x have no verified complete fix and must be upgraded to a later release line to be secure.
Risk and Exploitability
The CVSS score of 8.6 signals a high‑severity problem, while the EPSS score of 1% indicates a currently low probability of exploitation. The flaw is not listed in the CISA KEV catalog. Exploitation requires the attacker first to attain code execution inside the Dependabot container, which is a non‑trivial prerequisite. Once that occurs, the attacker can write an arbitrary workflow file, which will then be executed if the repository runs pull_request_target or auto‑merge workflows. Although the chance of exploitation is limited, the potential impact—confidentiality disclosure and arbitrary code execution—remains significant.