Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

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

High8.6EPSS 1.2%
Published
Updated
Reserved
Assigned by
GitHub_P

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.

Timeline

  1. ID reserved

    By GitHub_P

  2. · 8 days later

    Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-15343, by who scored it
Scored byCVSSScoreVector
GitHub_PCNA (assigner)4.0High8.6CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
NVDNVD · Deferred4.0High8.6CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS (exploitation in 30 days)
1.2% · top 32% of all CVEs (7 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.6.

Weakness

Affected products

  • GitHub · Enterprise Server

    • affected 3.17.0 – < 3.17.*
    • affected 3.18.0 – < 3.18.*
    • affected 3.19.0 – < 3.19.*
    • affected 3.20.0 – < 3.20.*
    • affected 3.21.0 – < 3.21.*
    • affected 3.22.0 – < 3.22.*

What to do

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.

References (9)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-15343 badge
[![CVE-2026-15343](https://trackcve.app/badge/CVE-2026-15343.svg)](https://trackcve.app/cve/CVE-2026-15343)

Record last updated .