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

Published Jul 17, 2026 CVSS 4.0 · 8.6 High EPSS 1.2% KEV · Not listed
Description
A path traversal vulnerability was identified in GitHub Enterprise Server that allowed an attacker with code execution inside a Dependabot updater container to write files to arbitrary repository paths, including GitHub Actions workflow files under .github/workflows/, because path validation did not check the actual write destination. The initial fix in versions 3.21.3, 3.20.5, 3.19.9, 3.18.12, and 3.17.18 was incomplete because validation checked the supplied symlink target, while the publisher wrote the file using its directory and name. Writing GitHub Actions workflow files required the Dependabot installation to have workflows: write permission. Depending on repository permissions and workflow configuration, including a relevant pull_request_target workflow or auto-merge, an injected workflow could execute with access to GitHub Actions secrets. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.23 and was fully fixed in versions 3.22.3, 3.21.8, 3.20.10, and 3.19.14. This vulnerability was reported via the GitHub Bug Bounty program.

Analysis

AI-generated

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.

Remediation

Vendor Solution

Upgrade to GitHub Enterprise Server 3.19.14, 3.20.10, 3.21.8, or 3.22.3, or a later patch release of the applicable release line. The previously announced fixes in 3.17.18, 3.18.12, 3.19.9, 3.20.5, and 3.21.3 were incomplete and do not fully remediate this vulnerability. No complete fix is available for the 3.17 or 3.18 release lines; users of those lines must upgrade to a release containing the complete fix.


OpenCVE Recommended Actions

  • Upgrade GitHub Enterprise Server to version 3.19.14, 3.20.10, 3.21.8, or 3.22.3 or later to apply the complete path‑traversal fix.
  • If an upgrade is not immediately possible, ensure that Dependabot installations do not have the workflows:write permission and disable or restrict the use of pull_request_target or auto‑merge workflows that run untrusted code.
  • Regularly audit repository directories for newly added .github/workflows files, remove any that are not part of approved workflows, and monitor logs for attempts to create or modify workflow files.

Generated by OpenCVE AI on November 4, 2026 at 15:10 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description 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 pull_request_target 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. A path traversal vulnerability was identified in GitHub Enterprise Server that allowed an attacker with code execution inside a Dependabot updater container to write files to arbitrary repository paths, including GitHub Actions workflow files under .github/workflows/, because path validation did not check the actual write destination. The initial fix in versions 3.21.3, 3.20.5, 3.19.9, 3.18.12, and 3.17.18 was incomplete because validation checked the supplied symlink target, while the publisher wrote the file using its directory and name. Writing GitHub Actions workflow files required the Dependabot installation to have workflows: write permission. Depending on repository permissions and workflow configuration, including a relevant pull_request_target workflow or auto-merge, an injected workflow could execute with access to GitHub Actions secrets. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.23 and was fully fixed in versions 3.22.3, 3.21.8, 3.20.10, and 3.19.14. This vulnerability was reported via the GitHub Bug Bounty program.
References
Type Values Removed Values Added
First Time appeared Github
Github enterprise Server
Vendors & Products Github
Github enterprise Server
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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 pull_request_target 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.
Title 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
Weaknesses CWE-22
References
Metrics cvssV4_0

{'score': 8.6, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Sources

Status
PUBLISHED
Assigner
GitHub_P
Published
Updated
Nov 3, 2026, 10:48 PM
Reserved
Jul 9, 2026, 8:11 PM
Status
Deferred
Published
Jul 17, 2026, 4:17 PM
Modified
Nov 3, 2026, 11:17 PM