NCCapital

A critical vulnerability in GitHub’s internal Git infrastructure briefly put millions of repositories at risk, according to newly published research from Wiz and GitHub’s own security response. The flaw, tracked as CVE-2026-3854, affected GitHub.com, GitHub Enterprise Cloud, and GitHub Enterprise Server. Wiz researchers said the issue allowed remote code execution through a crafted git push command, using a standard Git client and a flaw in how GitHub handled internal metadata during push operations. The vulnerability centered on Git push options. GitHub explained that user-supplied push option values were incorporated into internal metadata without enough sanitization. Because the metadata format used a delimiter character that could also appear in user input, an attacker could inject additional fields that downstream services treated as trusted internal values. Wiz said the impact was especially serious because the bug could have enabled command execution on shared GitHub.com storage nodes. The researchers reported that millions of public and private repositories were accessible on affected backend nodes, though Wiz said it validated the exposure using its own test accounts and did not access other users’ repository contents. GitHub said the vulnerability was reported through its bug bounty program on March 4, 2026. The company said it reproduced the issue internally within 40 minutes, deployed a fix to GitHub.com in under two hours, and began a forensic investigation. GitHub says that investigation found no evidence of exploitation outside Wiz’s testing and no evidence that customer data was accessed, modified, or exfiltrated. For regular GitHub.com users, no action is required because GitHub says the hosted service was patched on March 4. The bigger concern is for GitHub Enterprise Server administrators. GitHub recommends upgrading to a patched release immediately and reviewing audit logs for suspicious push operations containing semicolons in push options. Wiz reported that GitHub Enterprise Server instances were still widely exposed at the time of disclosure, saying its data indicated that 88% of instances had not yet been updated. GitHub’s patched versions include GHES 3.14.25 or later, 3.15.20 or later, 3.16.16 or later, 3.17.13 or later, 3.18.7 or later, 3.19.4 or later, and 3.20.0 or later. The incident is also notable because Wiz says the vulnerability was discovered with AI-assisted reverse engineering tools. That matters beyond GitHub: as attackers and researchers use AI to examine closed-source systems more quickly, companies may face faster discovery of deep infrastructure bugs that previously required much more manual reverse engineering. The practical takeaway is simple: GitHub.com users are covered, but GitHub Enterprise Server customers should patch now. For security teams, CVE-2026-3854 is a reminder that internal service protocols, metadata parsing, and trusted backend assumptions can become major attack surfaces when user-controlled input is not strictly sanitized.