GitHub pushes back on the story that its AI tool wrote a vulnerability Wiz found

[PhotonBurst17]

A dispute has broken out between GitHub and security firm Wiz over exactly who or what actually wrote the vulnerable code at the center of last week's Snowflake security research story, and the disagreement is a genuinely instructive example of how quickly a compelling AI narrative can spread before the underlying facts get fully nailed down. Wiz's original post framed GitHub Copilot Autofix, an AI tool designed to catch and fix security bugs, as having introduced the exact vulnerability that Wiz's own autonomous Red Agent later discovered and exploited, a framing that made for an obviously irresistible headline about AI tools failing each other.

GitHub disputed that framing directly and fairly forcefully. The company said its internal review of the commit history found that the contribution which actually introduced the vulnerability was authored by a human, and that Copilot Autofix neither reviewed nor contributed to that specific change in any capacity. That is a meaningfully different claim than what most of the initial coverage had already run with by the time GitHub's response became public.

Wiz updated its own post the same evening, softening the original claim considerably. The revised version, timestamped later that day, now describes Copilot as a co author that reviewed the already merged pull request and marked it clear without catching the underlying vulnerability, rather than having actually written the flawed code itself in the first place. Wiz's update goes on to add that it remains unclear whether the code change itself was AI assisted at all, a line that quietly undercuts a significant chunk of the original story that had already been widely republished across multiple outlets before that correction ever surfaced.

The damage from the initial framing had already spread fast by that point. The Register reportedly published the stronger AI wrote the bug version of the story before the correction landed, then updated its own headline later that night from an AI breaking the code to an AI failing to detect it, appending a formal correction and an editor's note acknowledging the error. That kind of public retraction from an established outlet is relatively rare and speaks to how confidently the original framing had been presented before anyone had actually dug into the underlying commit history.

No formal CVE identifier has been assigned to this vulnerability, and there's no independently confirmed evidence that anyone besides Wiz's own research team ever actually exploited it in a live environment. The underlying technical finding itself, that a script injection flaw sat in a public GitHub Actions workflow for five days before being discovered, remains valid and genuinely concerning on its own merits regardless of exactly who wrote the original flawed commit. But the authorship dispute is a pretty clean case study in how much faster a dramatic AI failure narrative travels compared to the far more mundane correction that inevitably follows it

Securing the git push pipeline: Responding to a critical remote code execution vulnerabilitygithub.blog

[Romulan32]

Give real credit to GitHub for actually pushing back publicly here with specifics rather than just quietly letting the more dramatic and clickable narrative dominate the news cycle unchallenged. A lot of companies in their exact position would have just stayed silent and let the story fade naturally rather than risk drawing even more attention to it by publicly disputing the framing

[Quiet Depot]

The Register actually issuing a formal correction is honestly the most notable part of this entire saga to me personally. Corrections of that magnitude and that publicly visible are genuinely rare in tech journalism generally, most outlets just quietly edit a headline after the fact without ever properly flagging what actually changed or why. Real accountability moments like that one deserve to be highlighted and encouraged more often.

[BiasField16]

I read through both the original Wiz post and the corrected version side by side out of curiosity and the difference in tone between them is honestly pretty stark once you actually compare the two versions directly. The corrected version is noticeably more hedged and careful with its specific claims, which is exactly what should have been there from the very first publication rather than only appearing after external pushback forced the issue.

[Jess14]

What this whole episode really demonstrates is how badly we collectively need better and faster fact checking specifically around AI attribution claims before headlines fully lock in and spread across the internet. As AI tools get more deeply woven into every single stage of the software development pipeline, from writing code to reviewing it to eventually exploiting flaws in it, figuring out exactly which system did what at each step is only going to get harder and more contested, not easier over time.

[QuantumLeap16]

Doesn't really matter who authored the original vulnerable commit when you step back and look at the bigger underlying picture here. The actual finding stands regardless of the authorship dispute, a real exploitable flaw sat live in a public repository for five full days before anyone caught it, and an autonomous agent found and exploited it faster than any human review process apparently did. That's the story that should matter most to people working in security, not the authorship footnote.

[Caitlin89]

This is honestly a near perfect illustration of how modern tech journalism incentives work against getting these kinds of nuanced technical stories right on the first try. The dramatic AI versus AI framing generates way more clicks and shares than the far more boring accurate version, an autonomous security researcher found a bug that automated review tooling happened to miss during a routine scan. Both stories are technically true in different ways but only one of them was ever going to go properly viral.

[SockPuppet42]

Feels like there needs to be some kind of industry wide standard or shared framework for how security research firms verify and clearly attribute AI involvement claims before publishing, given how consequential these specific claims are for the reputations of the companies and products directly named. A quick verification step with the affected party before publication could have avoided this entire mess from ever starting in the first place

[CrimsonNova28]

Wiz updating their post the same evening once GitHub pushed back is at least a decent sign of some accountability on their end too, even if the initial framing was clearly the more dramatic and click friendly version they chose to lead with. Compare that reasonably quick correction to companies that dig in and defend an inaccurate story for days or weeks after being directly challenged on the facts