GitHub Enterprise Server: Path Traversal (CVE-2026-15343)
Published Last modified Sources: CVE.org, BSI
What is affected, what to do
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.
Update GitHub Enterprise Server to version 3.19.9.
- Affected
- GitHub Enterprise Server
gte 3.17.0..* - GitHub Enterprise Server
gte 3.18.0..* - GitHub Enterprise Server
gte 3.19.0..* - GitHub Enterprise Server
gte 3.20.0..* - GitHub Enterprise Server
gte 3.21.0..* - GitHub Enterprise Server
gte 3.22.0..*
- GitHub Enterprise Server
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
8.6
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v4
8.6
CVSS v4
Severity High on the scale from 0 to 10.
Source: CVE.org, BSI
1.2 %
EPSS score
Moderate — model estimates 1-10% exploitation likelihood.
Source: FIRST EPSS, percentile 68.2
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 100.57 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 8.6 Methodology
CVSS v4
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 8.6
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 1.2 %
- Moderate — model estimates 1-10% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 68.2
- High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
- CISA assessment (SSVC)
- Exploitation: none known · not automatable · Technical impact: total
- Source: CISA Vulnrichment, as of 17 July 2026
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-22
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
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.
Source: cvelistv5, NVD (NIST), BSI CSAF, BSI WID Portal
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| GitHub | Enterprise Server |
|
|
| Microsoft | GitHub Enterprise Server |
|
|
Vendors and products
Weakness classes (CWE)
CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Base
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Entry at MITRE CWE-22
References & sources
- docs.github.comGitHub Enterprise Server 3.17.18 release notes: original incomplete fixRelease notes, x_incomplete-fix
- docs.github.comGitHub Enterprise Server 3.18.12 release notes: original incomplete fixRelease notes, x_incomplete-fix
- docs.github.comGitHub Enterprise Server 3.19.9 release notes: original incomplete fixRelease notes, x_incomplete-fix
- docs.github.comGitHub Enterprise Server 3.20.5 release notes: original incomplete fixRelease notes, x_incomplete-fix
- docs.github.comGitHub Enterprise Server 3.21.3 release notes: original incomplete fixRelease notes, x_incomplete-fix
- docs.github.comGitHub Enterprise Server 3.19.14 release notes: complete fix, November 3, 2026Release notes, Patch
- docs.github.comGitHub Enterprise Server 3.20.10 release notes: complete fix, November 3, 2026Release notes, Patch
- docs.github.comGitHub Enterprise Server 3.21.8 release notes: complete fix, November 3, 2026Release notes, Patch
- docs.github.comGitHub Enterprise Server 3.22.3 release notes: complete fix, November 3, 2026Release notes, Patch
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedgithub.com
Description added or changed
New references:- https://docs.github.com/en/enterprise-server@3.17/admin/release-notes#3.17.18
- https://docs.github.com/en/enterprise-server@3.18/admin/release-notes#3.18.12
- https://docs.github.com/en/enterprise-server@3.19/admin/release-notes#3.19.14
- https://docs.github.com/en/enterprise-server@3.19/admin/release-notes#3.19.9
and 5 more references
Show 16 original changes
Individual changes of this event as published by NVD Type Action Before After Description changed 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.Affected versions (publisher) added —Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/15xxx/CVE-2026-15343.json">CVE-2026-15343</a>Reference added —https://docs.github.com/en/enterprise-server@3.17/admin/release-notes#3.17.18Reference added —https://docs.github.com/en/enterprise-server@3.18/admin/release-notes#3.18.12Reference added —https://docs.github.com/en/enterprise-server@3.19/admin/release-notes#3.19.14Reference added —https://docs.github.com/en/enterprise-server@3.19/admin/release-notes#3.19.9Reference added —https://docs.github.com/en/enterprise-server@3.20/admin/release-notes#3.20.10Reference added —https://docs.github.com/en/enterprise-server@3.20/admin/release-notes#3.20.5Reference added —https://docs.github.com/en/enterprise-server@3.21/admin/release-notes#3.21.3Reference added —https://docs.github.com/en/enterprise-server@3.21/admin/release-notes#3.21.8Reference added —https://docs.github.com/en/enterprise-server@3.22/admin/release-notes#3.22.3Reference removed https://docs.github.com/en/enterprise-server@3.17/admin/release-notes#3.17.18—Reference removed https://docs.github.com/en/enterprise-server@3.18/admin/release-notes#3.18.12—Reference removed https://docs.github.com/en/enterprise-server@3.19/admin/release-notes#3.19.9—Reference removed https://docs.github.com/en/enterprise-server@3.20/admin/release-notes#3.20.5—Reference removed https://docs.github.com/en/enterprise-server@3.21/admin/release-notes#3.21.3—Source identifier: product-cna@github.com
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: none known, automatable: no
Show the original change
Individual changes of this event as published by NVD Type Action Before After SSVC assessment added —{"id":"CVE-2026-15343","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-07-17T16:31:35.938532Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
One NVD translation into another language is hidden.
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-15343"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-15343.svg?lang=en" alt="CVE-2026-15343 – NEOSEC Intel" height="20"></a>