6 items
Google's criminal AI zero-day confirms the new attack topology: AI compressed bug discovery to near-zero cost, but the attacker still needed credentials and the patch cycle still ran in days. The asymmetric trade sits in IAM hardening and patch-velocity infrastructure. The AI-security pure-plays are already priced for the headline; the credential layer is what actually moved.
AI compressed vulnerability discovery to near-zero cost; credentialed access remained the second gate. Google's disclosure of the first criminal AI-enabled zero-day is the empirical confirmation that the offense-side binding constraint has shifted from bug-finding to credential acquisition, which re-rates the IAM stack more cleanly than the AI-security pure-plays. Rob Joyce's "fingerprint at the crime scene" line points to a parallel category in forensic AI-authorship detection that remains structurally unfilled.
Coordinated disclosure was an information-containment regime, and containment fails when discovery diffuses. Eleven independent researchers landed the same critical bug in six weeks; Copy Fail took roughly an hour of AI-assisted scanning to find; Dirty Frag's embargo collapsed within hours via unrelated rediscovery, with Microsoft Defender confirming in-the-wild exploitation a day later. The offense side has integrated LLMs into exploit pipelines. The defense and policy layer largely has not, and that asymmetry is the actual risk — CVE feeds are now lagging artifacts, and patch-diff intelligence is the signal that matters.
RedAccess found over 5,000 exposed apps across the four leading vibe-coding platforms, with roughly 2,000 leaking real PHI, customer chat logs, and internal strategy decks. These aren't misconfigured storage buckets; they're auth logic the platform generated and the user never saw. The S3 analogy that's circulating misses the legal novelty: AWS could credibly disclaim your bucket policy because you wrote it. Lovable, Replit, and Base44 wrote the auth logic that isn't there. That shifts where liability attaches, and the first court to hold a code-generation platform partially liable for a generated vulnerability resets every product roadmap in the category overnight. It's the same verification failure the hedge fund and interpretability stories surface from different angles: the layer that was supposed to enforce quality or security has been dissolved by the technology it was meant to govern. The people building trust infrastructure for that layer, across all three markets, are the ones with a durable position.
RedAccess found 5,000-plus exposed apps on the four leading vibe-coding platforms with around 2,000 leaking real PHI, customer chat logs, and strategy decks. The S3 analogy is reaching for the right pattern but missing the legal twist: AWS could credibly say it didn't write your bucket policy. Lovable, Replit, and Base44 wrote the auth logic that doesn't exist. The first court that holds a code-generation platform partially liable for a generated vulnerability resets the entire industry's product roadmap overnight.
A UK government lab confirmed Mythos can autonomously execute a 32-step corporate network attack end-to-end, outperforming every tested model including GPT-5, with performance still scaling at the 100M token ceiling. The evaluation tested capability against undefended ranges, so what AISI validated is threat potential, not operational impact against a real defended environment. The structural shift is that government evaluation infrastructure is becoming the third-party verification layer for frontier AI claims, sitting between self-reported lab benchmarks and the market the way FDA trials sit between pharma and prescribers.
