CVE-2026-17556: Unauthenticated arbitrary file deletion via path traversal in GitHub Enterprise Server
- Vendor
- GitHub
CVE-2026-17556 is a high-severity path traversal vulnerability in GitHub Enterprise Server. The flaw arises because the X-GitHub-Request-Id HTTP request header was used without sanitization as a filesystem path segment for an upload buffer directory. By supplying traversal sequences in that header, a remote attacker could cause the buffer path to resolve to an arbitrary location on the appliance filesystem. A deferred cleanup routine would then recursively delete the attacker-selected target path. As a result, an unauthenticated attacker could remotely delete arbitrary files and directories on the instance, including the user storage directory that holds Git LFS objects, release assets, attachments, and avatars. All GitHub Enterprise Server versions prior to 3.22 are affected; fixes were released in 3.21.4, 3.20.6, 3.19.10, 3.18.13, and 3.17.19.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows unauthenticated remote deletion of arbitrary files and directories on the GitHub Enterprise Server instance. The impact includes destructive loss of repository-adjacent stored content such as Git LFS objects, release assets, attachments, and avatars, and can extend to broader service disruption depending on which filesystem locations are removed. The vulnerability affects integrity and availability rather than confidentiality, and can result in severe operational damage and data loss.
Mitigation
If you can’t patch tonight, do this now.
No vendor workaround is specified. Until patched versions can be deployed, reduce exposure by restricting network reachability to the GitHub Enterprise Server instance to trusted administrative or corporate networks only, and minimize unauthenticated access paths. Because exploitation does not require authentication and remains possible even in private mode, access-control and network-layer restrictions are the primary temporary mitigation.
Remediation
Patch, then assume compromise.
Upgrade GitHub Enterprise Server to a fixed release in the relevant supported branch: 3.21.4, 3.20.6, 3.19.10, 3.18.13, or 3.17.19. More generally, move to version 3.22 or later, or the vendor-provided patched build for the deployed release line.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-17556 exploited in the wild?
- As of Sep 25, 2026, Mallory has no reports of CVE-2026-17556 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-17556?
- As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-17556.
- Is there a patch for CVE-2026-17556?
- Upgrade GitHub Enterprise Server to a fixed release in the relevant supported branch: 3.21.4, 3.20.6, 3.19.10, 3.18.13, or 3.17.19. More generally, move to version 3.22 or later, or the vendor-provided patched build for the deployed release line.
- What products are affected by CVE-2026-17556?
- GitHub Enterprise Server.
- How severe is CVE-2026-17556?
- CVE-2026-17556 has a CVSS v4 score of 8.8 (High) and an EPSS score of 0.80% (58th percentile) as of Sep 25, 2026.
Recent activity
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.