CVE-2026-15343: Path traversal vulnerability in GitHub Enterprise Server allowed writing files to arbitrary repository paths, including GitHub Actions workflow files, via unchecked Dependabot dependency-file paths
A path traversal vulnerability was identified in GitHub Enterprise Server that allowed an attacker who had code execution inside the Dependabot updater container to write files to arbitrary repository paths, including GitHub Actions workflow files under .github/workflows/ as the path validation did not check the effective path which the attacker could control through the dependency file's directory and symlink target. If the repository used a pullrequesttarget workflow or had auto-merge enabled, an injected workflow could execute with access to the repository's GitHub Actions secrets. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.22 and was fixed in versions 3.21.3, 3.20.5, 3.19.9, 3.18.12, 3.17.18.
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.22
Event History
Frequently Asked Questions
What is the severity of CVE-2026-15343?
The severity of CVE-2026-15343 is high with a CVSS score of 8.6.
How do I fix CVE-2026-15343?
To fix CVE-2026-15343, update your GitHub Enterprise Server to the latest version where the vulnerability is patched.
What type of vulnerability is CVE-2026-15343?
CVE-2026-15343 is a path traversal vulnerability that affects GitHub Enterprise Server.
What can an attacker do with CVE-2026-15343?
An attacker can exploit CVE-2026-15343 to write files to arbitrary repository paths, potentially compromising GitHub Actions workflow files.
How does CVE-2026-15343 affect GitHub Enterprise Server?
CVE-2026-15343 affects GitHub Enterprise Server by allowing unauthorized file writing due to unchecked Dependabot dependency-file paths.