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
·
Updated

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 pullrequesttarget 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.

Affected Software

1 affected component
GitHub GitHub Enterprise Server<3.23

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.19.14
  2. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.20.10
  3. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.21.8
  4. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.22.3

Event History

Jul 17, 2026
CVE Published
via MITRE·03:18 PM
Data Sourced
via MITRE·03:18 PM
RemedyDescriptionWeakness
Data Sourced
via NVD·04:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2026-15343?

The severity of CVE-2026-15343 is high with a CVSS score of 8.6.

2

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.

3

What type of vulnerability is CVE-2026-15343?

CVE-2026-15343 is a path traversal vulnerability that affects GitHub Enterprise Server.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203