Amazon's MadPot honeypot network recorded an exploitation attempt against what is now tracked as CVE-2026-109618 and CVE-2026-109619 — nicknamed PHP2Shell — on October 17, 2026, four days before the vendor publicly disclosed the flaw. The request came from a commercial anonymization network, suggesting a threat actor had working exploit code ahead of the official embargo lift. When the embargo ended on October 21 at 1400 UTC, AWS says proof-of-concept code and real attack traffic hit its sensors within hours, from several distinct sets of infrastructure. AWS argues this points to a structural shift: AI-assisted analysis is making it faster to turn a patch or advisory into a working exploit, shrinking the old assumption that most attacks follow a public PoC.
AWS tested its AWS Security Agent (now part of AWS Continuum) against a freshly built benchmark of 37 real, recently disclosed CVEs, each run as a live containerized target with a hidden flag. Starting from a low-privilege endpoint with only a one-line hint and no proof-of-concept, the agent, running on Claude Opus 5, captured 33 of 37 flags through genuine end-to-end exploitation after an integrity audit, with 2 captures reclassified as unintended-path solves and 2 genuine misses where the agent broke the target before extracting the flag. AWS built this benchmark to avoid the contamination problem of public CVE suites, which models may have memorized from training data.
Microsoft Threat Intelligence documented exploitation of CVE-2026-73570, an unauthenticated OS command-injection flaw in the Zimbra Collaboration Suite's SNMP notification path. Attackers triggered it via specially crafted emails against internet-facing servers running the optional zimbra-snmp package with SNMP notifications enabled, requiring no authentication or user interaction. Post-exploitation activity included JSP webshell deployment, privilege escalation to root, persistent access, credential and mailbox theft, lateral movement across Zimbra clusters, and custom remote-access malware. Zimbra fixed the issue in version 10.1.20 (released July 20, 2026); the CVE was publicly disclosed August 13, 2026, and Microsoft observed scanning and exploitation activity during the gap between patch availability and disclosure, as well as after.