Someone found a vulnerability. Company patched the vulnerability, but messed up in the process.
The vulnerability was identified by AI. Not clear if the company used AI to write the patch. But the role of AI is irrelevant - the result was a broken system. Their testing should have caught the regression. If it didn't, they have bad tests.
This is a testing/QA failure, orthogonal to AI issues. I don't deny that the pace of AI-revealed vulnerabilities increases the pressure to rush out patches. But the response to vulnerabilities is entirely in the hands of the operators and test writers who botched this one.
It's not unreasonable to assume either way sadly. Some areas of code development still may outright prohibit the use of AI genrated code, if a developer listens or not before just asking chatGPT is another thing. Other areas are pushing their developers to write no code at all, only prompt the AI and not even try to fix it themselves if people are to be believed.
Only people who will get anything close to a real answer are the people who get to read a forensic level postmortum on these incidents.
> Wall Street executives and the National Security Agency have told members of Congress that this week’s widespread tech outages were caused by attempts to fix vulnerabilities identified by artificial intelligence, according to three sources familiar with the private conversations.
aka, possibly rushed patches/patching, in response to AI-discovered vulns. As far as I can tell "AI-authored patches" is not really mentioned in this article. (Whether that's true or not, I won't say, but it's weird to see the first comments just jumping on "AI patching bad".)