Loading vulnerability…
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.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.