Reverse Engineering With AI Unearths High-Severity GitHub Bug TechTarget and Informa Tech’s Digital Business Combine.TechTarget and InformaTechTarget and Informa Tech’s Digital Business Combine.Together, we power an unparalleled network of 220+ online properties covering 10,000+ granular topics, serving an audience of 50+ million professionals with original, objective content from trusted sources. We help you gain critical insights and make more informed decisions across your business priorities.Dark Reading Resource LibraryBlack Hat NewsOmdia CybersecurityAdvertiseNewsletter Sign-UpNewsletter Sign-UpCybersecurity TopicsRelated TopicsApplication SecurityCybersecurity CareersCloud SecurityCyber RiskCyberattacks & Data BreachesCybersecurity AnalyticsCybersecurity OperationsData PrivacyEndpoint SecurityICS/OT SecurityIdentity & Access Mgmt SecurityInsider ThreatsIoTMobile SecurityPerimeterPhysical SecurityRemote WorkforceThreat IntelligenceVulnerabilities & ThreatsRecent in Cybersecurity TopicsСloud SecurityHackers Use AI for Exploit Development, Attack AutomationHackers Use AI for Exploit Development, Attack AutomationbyAlexander CulafiMay 11, 20264 Min ReadСloud SecurityAfter Replacing TeamPCP Malware, 'PCPJack' Steals Cloud SecretsAfter Replacing TeamPCP Malware, 'PCPJack' Steals Cloud SecretsbyNate NelsonMay 7, 20265 Min ReadWorld Related TopicsDR GlobalMiddle East & AfricaAsia PacificLatin AmericaSee AllThe EdgeDR TechnologyEventsRelated TopicsUpcoming EventsPodcastsWebinarsSEE ALLResourcesRelated TopicsResource LibraryNewslettersPodcastsReportsVideosWebinarsWhite Papers Partner PerspectivesDark Reading Resource LibraryApplication SecurityСloud SecurityVulnerabilities & ThreatsCyber RiskNewsReverse Engineering With AI Unearths High-Severity GitHub BugWiz used an AI reverse-engineering tool to pinpoint a vulnerability that previously would have been too costly and time-consuming to undertake.Alexander Culafi,Senior News Writer,Dark ReadingApril 29, 20263 Min ReadSource: Klaus Ohlenschlaeger via Alamy Stock PhotoGitHub yesterday disclosed CVE-2026-3854, a high severity (8.7 CVSS) vulnerability identified in GitHub Enterprise Server that would grant an attacker with push access to a repository to achieve remote code execution. GitHub said in a blog post that the vulnerability also affected github.com, GitHub Enterprise Cloud, GitHub Enterprise Cloud with Data Residency, and GitHub Enterprise Cloud with Enterprise Managed Users. Cloud security firm Wiz reported the vulnerability March 4 through GitHub's bug bounty program. GitHub said that, in less than two hours, it validated the finding, pushed a fix to github.com, and, after an investigation, concluded no exploitation had taken place. While a remote code execution bug generally is worth calling attention to, the circumstances here are particularly noteworthy, as Wiz explained in its blog post. It's "one of the first critical vulnerabilities discovered in closed-source binaries using AI, highlighting a shift in how these flaws are identified."Related:'TrustFall' Convention Exposes Claude Code Execution RiskHow CVE-2026-3854 WorksAs GitHub's Alexis Wales put it in the company's disclosure blog, user-pushed code in GitHub passes multiple internal services. Metadata, such as repository type and the environment it should be pushed in, is passed between services via an internal protocol. "The vulnerability leveraged how user-supplied git push options were handled within this metadata. Push options are an intentional feature of git that allow clients to send key-value strings to the server during a push," she wrote. "However, the values provided by the user were incorporated into the internal metadata without sufficient sanitization. Because the internal metadata format used a delimiter character that could also appear in user input, an attacker could inject additional fields that the downstream service would interpret as trusted internal values."Wiz demonstrated that an attacker could chain several of these values together to bypass various protections and internal limitations to execute remote code.GitHub and Wiz both advise GitHub Enterprise Server customers to upgrade to a fixed version (3.14.24, 3.15.19, 3.16.15, 3.17.12, 3.18.6 and 3.19.3); contrary to other affected products, Enterprise Server requires an authenticated user with push access to patch. GitHub Enterprise Cloud, GitHub Enterprise Cloud with Enterprise Managed Users, GitHub Enterprise Cloud with Data Residency, and github.com have been patched, and no user intervention is required. In Wiz's blog post, security researcher Sagi Tzadik urged impacted users to upgrade, noting 88% of instances remained vulnerable at the time of publication.Related:Fresh Wave of GlassWorm VS Code Extensions Slices Through Supply ChainAI Reverse-Engineered Vulnerability DiscoveryTzadik wrote that Wiz had previously hunted for vulnerabilities on GitHub Enterprise Server, but "extracting and auditing the sheer volume of compiled blackbox binaries that run this pipeline historically required an impractical amount of time and manual effort."Enter IDA MCP, an AI-powered assistant used for vibe reverse-engineering code. It allowed Wiz to do what was previously "too costly," the blog explained, such as rapidly analyzing GitHub's compiled binaries, reconstructing internal protocols, and systematically identifying where user input could influence server behavior. In an email, Tzadik tells Dark Reading that Wiz has been "chasing this target since September 2024," but couldn't justify the resources required to do the reverse-engineering work. "It likely would have taken weeks, maybe months, of dedicated time and focus. With the help of AI tools, it took less than 48 hours to go from idea to a working exploit," he says.The closed source element of GitHub is also important, the researcher says, because closed source software historically has been home to the biggest security risks and the most obscurity. "As the latest AI models have improved, it's become much easier, faster, and cheaper to do things like reverse-engineer closed-source binaries, or produce a working exploit from a CVE identifier and a git commit hash as input," Tzadik explains. "Scale is also a factor — while researchers used to work on a limited set of projects at a given time, these days it is possible to run automated pipelines on multiple targets at once."Related:Vercel Employee's AI Tool Access Led to Data BreachAbout the AuthorAlexander CulafiSenior News Writer, Dark ReadingAlex is an award-winning writer, journalist, and podcast host based in Boston. After cutting his teeth writing for independent gaming publications as a teenager, he graduated from Emerson College in 2016 with a Bachelor of Science in journalism. He has previously been published on VentureFizz, Search Security, Nintendo World Report, and elsewhere. In his spare time, Alex hosts the weekly Nintendo podcast Talk Nintendo Podcast and works on personal writing projects, including two previously self-published science fiction novels.See more from Alexander CulafiWant more Dark Reading stories in your Google search results?Add Us NowMore InsightsIndustry ReportsHow Enterprises Are Developing Secure ApplicationsInside RSAC 2026: security leaders reveal the risks redefining your defense strategyHow Enterprises Are Harnessing Emerging Technologies in CybersecurityDitch the Data Center: Understanding Flexible Cloud Infrastructure Security Management2025 State of MalwareAccess More ResearchWebinarsThe New Attack Surface: How Attackers Are Exploiting OAuth to Own Your Cloud WorkspacePrompt Injection Is Just the Start: Securing LLMs in AI SystemsAnatomy of a Data Breach: What to Do if it Happens to YouHow Well Can You See What's in Your Cloud?Implementing CTEM: Beyond Vulnerability ManagementMore WebinarsEditor's ChoiceThreat IntelligenceFrom Stuxnet to ChatGPT: 20 News Events That Shaped CyberFrom Stuxnet to ChatGPT: 20 News Events That Shaped CyberbyDark Reading Editorial TeamMay 6, 202631 Min ReadCyber RiskPhysical Cargo Theft Gets a Boost From CybercriminalsPhysical Cargo Theft Gets a Boost From CybercriminalsbyRobert LemosMay 4, 20265 Min ReadWant more Dark Reading stories in your Google search results?Keep up with the latest cybersecurity threats, newly discovered vulnerabilities, data breach information, and emerging trends. Delivered daily or weekly right to your email inbox.SubscribeRSAC 2026: key news & insightsAt RSAC 2026, Dark Reading captured critical intelligence on AI, new attack methods, geopolitics, and much moreGet Your RecapWebinarsThe New Attack Surface: How Attackers Are Exploiting OAuth to Own Your Cloud WorkspaceWed, June 24,2026 at 1pm ESTPrompt Injection Is Just the Start: Securing LLMs in AI SystemsTues, May 26, 2026, at 1pm ESTAnatomy of a Data Breach: What to Do if it Happens to YouJune 18th, 2026 | 11:00am -5:00pm ET | Doors Open at 10:30am ETHow Well Can You See What's in Your Cloud?Thurs, June 4, 2026 at 1:00pm ESTImplementing CTEM: Beyond Vulnerability ManagementThurs, May 21, 2026 at 1pm ESTMore WebinarsBlack Hat USA | Mandalay Bay, Las VegasThe premier cybersecurity event of the year returns to Mandalay Bay with a re‑engineered, six‑day program built to ignite innovation, push boundaries, and bring the global security community together like never before. Use code: DARKREADING to save $200 on a Briefings pass or $100 on a Business pass.GET YOUR PASSDiscover MoreBlack HatOmdiaWorking With UsAbout UsAdvertiseReprintsJoin UsNewsletter Sign-UpFollow UsCopyright © 2026 TechTarget, Inc. d/b/a Informa TechTarget. This website is owned and operated by Informa TechTarget, part of a global network that informs, influences and connects the world’s technology buyers and sellers. All copyright resides with them. Informa PLC’s registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. TechTarget, Inc.’s registered office is 275 Grove St. Newton, MA 02466.Home|Cookie Policy|Privacy|Terms of UseYour Privacy Choices

This report details a significant vulnerability discovered in GitHub Enterprise Server, highlighting the increasing role of artificial intelligence in reverse engineering and security assessments. The vulnerability, CVE-2026-3854, was initially identified by Wiz, a cloud security firm, through GitHub’s bug bounty program. Wiz utilized an AI-powered reverse engineering tool, IDA MCP, to rapidly analyze GitHub’s compiled binaries, reconstruct internal protocols, and pinpoint the exploitable flaw within less than 48 hours – a timeframe that would have traditionally required weeks or even months of manual effort.

The vulnerability stemmed from the way user-pushed code handled metadata, specifically the incorporation of user-supplied git push options without sufficient sanitization. Wiz demonstrated the ability to chain these options to bypass internal protections and achieve remote code execution. The incident underscores the growing complexity of software supply chains, particularly those reliant on closed-source binaries, and the potential risks associated with these environments.

GitHub responded swiftly, validating the finding, applying a fix to github.com and other impacted products, and confirming that no exploitation had occurred. The rapid response reflects GitHub’s commitment to security and its responsiveness to external reports. Wiz’s research highlighted the shift in vulnerability discovery—previously a painstaking and costly endeavor—now achievable through intelligent automation. Sagi Tzadik, a researcher at Wiz, emphasized that this discovery represents "one of the first critical vulnerabilities discovered in closed-source binaries using AI," marking a significant change in the security landscape. He noted that the use of AI dramatically reduced the time required to identify and exploit the flaw, showcasing the transformative potential of AI in proactive security assessments. The vulnerability’s severity (8.7 CVSS) necessitates immediate action; GitHub advises customers to upgrade to fixed versions of GitHub Enterprise Server. The researcher estimates that 88% of instances remained vulnerable at the time of publication, emphasizing the ongoing importance of maintaining up-to-date security measures. Furthermore, the case highlights the broader trend of closed-source software presenting increased security risks, amplified by the accessibility of AI tools for reverse engineering.