AI agents are no longer just writing emails and answering support tickets. This month, they started breaking into networks. Google says an autonomous AI framework turned a public software patch into a working exploit with no human steering it, Amazon says AI agents exploited a zero-day and took root on a server in about 11 minutes, and CISA has flagged an AI gateway flaw that attackers are already using.
For US companies, the message is simple: the time between a security fix being published and an attacker using it is shrinking fast. Here is what happened, what it means for your business, and how to find your weak spots before an AI agent does.
The clearest warning came from Google's Q4 2026 AI Threat Tracker, published Nov. 16.
What Google found in the exploit_agent case
The framework is called exploit_agent. Google's threat hunters found it on an exposed staging server, configured to run continuous differential analysis on popular web application software. It compares code before and after a patch is announced, works out which flaw was closed, drafts an exploit and runs it automatically.
The Register reported the operator as suspected Russian-speaking, and the framework reportedly used Russian-language tooling. Google describes the attack as ending in data theft from victim organizations. The company did not name a group or country behind exploit_agent.
The number of victims and the extent of the data theft were not confirmed in the reporting reviewed for this story, and no US victim has been named.
How the patch-to-exploit pipeline works
Google says attackers have moved past manual prompting toward autonomous, multi-agent offensive frameworks. It named ARTEX, CAIRN, CyberStrikeAI and PentAGI, and other coverage of the report also names HexStrike AI. Google's report describes CAIRN in real intrusions that navigated attack paths against targets, including organizations in the US aerospace sector.
The design is what makes this case different. A security patch tells the world which code changed and why, and that diff works as a map of the bug. A system that can read the diff, draft an exploit and test it can follow the same logic a skilled researcher would, without the researcher in the room. CyberScoop quoted the Google Threat Intelligence Group's report on a system "to fully automate vulnerability discovery and exploitation without a human in the loop for the first time."
The word first deserves care. Google says it has not seen AI complete this whole patch-to-exploit sequence before. Commentators point out that this is a narrower claim than saying it was the first autonomous cyberattack anywhere. Treat it as Google's assessment of what it has observed, not as a settled record.
Why the timing forecast should change your patch schedule
Google forecasts that unsophisticated autonomous attacks could arrive within one to three months, and more advanced ones within three to six months. Aviatrix, in a separate vendor blog post, gives a similar window of about three months and six months. The exact figures differ between sources, so plan around the shorter number.
That changes the math for any team that patches on a monthly or quarterly cycle. A regular maintenance window still makes sense for routine updates, but it cannot be the default for internet-facing flaws that already have public details. Small IT departments that patch by hand gain no advantage here, because attacker tooling does not wait for a change board.
The same week brought parallel warnings. According to one trade report, the FBI and AWS both issued warnings about AI-agent attacks on the same day. Google's answer is commercial: Google Cloud announced AI Threat Defense, which combines Gemini, Wiz context, CodeMender patching and Mandiant expertise. In a Google Cloud blog post promoting the service, the company wrote, "Defending against machine-speed threats at human speed isn't feasible." That is vendor marketing, not independent analysis, but it frames the problem the same way the threat data does.
Two related AI-agent cases from the same week
Google's exploit_agent finding is separate from two other disclosures. On Nov. 20, Amazon described a zero-day in MONAI Label, a medical imaging software project, that AI agents exploited. Amazon's case involved a China-linked actor, which Amazon assessed with moderate confidence, and a university server in East Asia. The attack moved from API mapping to arbitrary file writes in about 11 minutes.
According to the project advisory, MONAI Label versions 0.8.5 and earlier are affected. Reporting conflicts on whether a fix exists. One outlet says no patch was released, while others say a fix shipped Nov. 18. A CVE identifier, CVE-2026-133968 with a CVSS score of 9.8, appears in only one source, so treat it as unconfirmed until the National Vulnerability Database or the project advisory shows it. USA 24 covered the Amazon disclosure in our earlier MONAI Label report.
The LiteLLM case is the second. CISA added CVE-2026-40217 to its Known Exploited Vulnerabilities catalog on Nov. 18, with a federal remediation deadline of Dec. 2, 2026. The flaw is a guardrail sandbox escape in LiteLLM, an AI gateway, and the fix is version 1.83.11, released Nov. 15. Sources disagree on the affected range, with some saying up to 1.83.9 and others up to 1.83.10. They also disagree on ransomware use: one report says ransomware use is known, while another says it is not confirmed.
| Case | Version or deadline | What to check |
|---|---|---|
| LiteLLM, CVE-2026-40217 | Fixed in 1.83.11 (released Nov. 15); federal deadline Dec. 2, 2026 | Gateway version, and which model keys it holds |
| MONAI Label | Versions 0.8.5 and earlier affected | Deployed versions; patch status is disputed in reporting |
| Google exploit_agent | Not tied to one product in Google's report | Vendor advisories for popular web application software you run |
The LiteLLM case shows why gateways deserve attention. A gateway that holds model keys touches many downstream services, so a flaw there reaches far. One claim circulating in coverage, that Google's threat team saw attackers turn limited LiteLLM keys into admin credentials, was not verified in the research for this story.
How to protect your company from AI agent attacks
Most of the defensive work is familiar. What has changed is the clock. Start with these steps:
- Patch internet-facing systems on a short clock. Google's pipeline works from fixes that are already public, so every day between release and deployment is exposure. Set a target window for critical internet-facing patches and document every exception.
- Inventory AI agents, chatbots, LLM gateways and API keys. Identify which ones touch production data, and rotate any keys that may have been exposed.
- Give agent tool calls least privilege. Block or restrict admin-level guardrail and test endpoints wherever you can.
- Monitor for automated attacks, and allow automated containment with human oversight. Amazon's security chief urged defenders to automate containment so responses can keep pace.
- Test yourself the way attackers now test, using authorized testing only.
Test yourself first: AI agents that attack your own systems
If attackers are using AI agents to find holes, the logical defense is to point the same kind of tools at your own systems first, with permission and on your schedule. That is the idea behind AI penetration testing. Bugcrowd describes it as a hands-on assessment that covers prompt injection, unsafe tool calls and data leakage, rather than signature-based scanning.
CyberHacker.ai is one US company offering this. The Dallas-based firm describes its approach as "AI agents that hack you first — before the real ones do," pairing autonomous AI attack agents with certified human testers it describes as OSCP and CEH level. According to the company:
- Fast start. Companies register online, paste in the domains, URLs and APIs they own, and book a test in about three minutes with a card, with no scoping call. Testing starts once the targets are verified, in windows of 2 to 72 hours or open-ended, and most tests finish within a few days.
- People check the findings. Every finding is confirmed by the company's team before the customer sees it, with a severity rating, a proof of concept and fix instructions.
- Retest and certificate. A finding closes only when a retest shows the fix holds. The engagement ends with a certificate that customers, partners or auditors can check at cyberhacker.ai/verify. The company notes that a certificate is not a warranty of a system's current state.
- Tests for your own AI. Its AI agent and chatbot pentest probes for direct and indirect prompt injection, jailbreaks, system prompt extraction, data leaks from knowledge bases, unsafe tool calls and privilege escalation through connected tools, against the full OWASP Top 10 for LLM applications. It covers agents built with LangChain, LlamaIndex, AutoGen, CrewAI and custom frameworks.
- Other services. Self-serve web app, API and web vulnerability tests, plus expert-led mobile, network, OT/SCADA/IoT, social engineering and desktop-software assessments.
- Published prices. One-time web app pentests are listed at $2,900 (Small), $4,900 (Medium) and $7,900 (Large), with Enterprise by quote and monthly plans available.
The company positions its reports as evidence for SOC 2, ISO 27001, PCI DSS, HIPAA, GDPR and the NIST Cybersecurity Framework, while stating the limit itself: "A penetration test is evidence, not a certification." The details above come from the company's website; USA 24 has not independently tested the service. Other automated and AI pentesting vendors include Horizon3.ai NodeZero, XBOW and Pentera. Whichever you choose, confirm the scope in writing, ask whether tests run against production or staging, and check with your auditor if you need the report for compliance.
What comes next for AI agent security and certification
The GAO report, released Nov. 20, found that the federal government has no agreed-upon way to certify AI tools meant to stop autonomous attacks, according to The Washington Times. That gap leaves buyers comparing AI security products without a shared yardstick. Expect vendors to fill the void with their own badges and claims, which is why independent evidence matters more than a logo.
Three things are worth watching over the coming weeks. First, whether the one-to-three-month forecast holds, and whether other vendors confirm full patch-to-exploit chains the way Google has described them. Second, whether the Dec. 2 LiteLLM deadline produces public evidence of exploitation. Third, how the MONAI Label patch question resolves, since a missing fix would leave deployments exposed with no clean remedy.
The bottom line: a checklist for this week
Google's report suggests the next wave of exposure will come from flaws that are already public, and AI agents are closing the gap between a fix and an attack. You do not need a large security team to get ahead of that, but you do need to start now:
- List everything you expose to the internet, including websites, APIs, VPNs, firewalls and AI chatbots.
- Set a patch deadline of days, not weeks, for critical flaws in those systems, starting with anything on CISA's Known Exploited Vulnerabilities list.
- Inventory your AI agents and API keys, remove the access they do not need, and rotate keys that may have leaked.
- Turn on alerts and automated blocking for obvious attacks, with a person reviewing what gets blocked.
- Test yourself before attackers do, with an authorized pentest of your most important app and any AI chatbot that touches customer data.
The companies that come through this wave in good shape will be the ones that found their own weak spots first.




