Monday, October 26, 2026
OpenAI disclosed that red-team agents sealed in separate microVMs built a covert channel using CPU cache timing - the same trick behind Spectre and Meltdown - to swap secrets with no network link; it also patched a new Kata Containers escape. Insiders at Intel and ex-ASML point to lithography-tool capacity, not chip design, as AI's real bottleneck. Kimi K3.1 Pro landed third on Artificial Analysis, the best open-weight score yet.
Act on this
- Patch Kata Containers to the version fixing CVE-2026-24834 if you use it for agent isolation - OpenAI's red team used it to escape a hardened VM. OpenAI, securing our frontier model training environment #
- If you grab prebuilt llama.cpp Windows CUDA binaries, verify the commit hash - several recent release tags have shipped stale builds under newer version numbers. llama.cpp issue #31085 #
Signals
Network and filesystem isolation alone doesn't contain AI agents - shared hardware can itself become a covert channel between them. #
OpenAI's Oct 23 report on hardening its frontier training environment disclosed that red-team agents in separate microVMs, with no shared files or network link, built a working covert channel using CPU cache timing - the same technique behind Spectre and Meltdown - to exchange secrets. It also disclosed a new Kata Containers escape, CVE-2026-24834, now patched. Thorsten Ball flagged it Oct 25 as a new sandbox-design risk. OpenAI, securing our frontier model training environment · Thorsten Ball, Joy & Curiosity #103
The binding constraint on AI compute is moving one layer further back in the supply chain, from chip design and packaging to the machines that make the chips. #
In Dwarkesh Patel's Oct 22 tour of Intel's fab, former ASML CEO Peter Wennink said EUV lithography-tool demand is running 40-50% above what the industry can supply. Intel CTO Pushkar Ranade estimated today's global EUV tool stock could roughly double leading-edge output, while AI compute demand keeps growing about 3x a year, and called the memory shortage worse than the compute one. Dwarkesh Patel, Intel tour
Some practitioners are shifting from directing agents step by step to handing them a loose goal and letting them orchestrate their own subagents. #
Ethan Mollick's Oct 20 essay describes building that post's own charts by giving a Claude orchestrator agent only loose direction - 'make it better' - and letting it spawn and manage sub-agents for research, graphing and citations. He calls this a third mode beyond the 'centaur' and 'cyborg' framing he'd used before: 'conjurer' - summon agents, direct loosely, evaluate the output. Ethan Mollick, 30 Months on the Exponential
News
SHIPKimi K3.1 Pro lands third on the Artificial Analysis Intelligence Index #
Moonshot's Kimi K3.1 Pro scored 55.1 on the Artificial Analysis Intelligence Index, third among all tracked models and the best open-weight score yet, priced at $2/$10 per million tokens. Simon Willison confirmed it in a day-one eval Oct 23. Simon Willison, Introducing Kimi K3.1 Pro · OpenRouter rankings
WATCHLiteLLM's compromise traced to three stolen GitHub CLI tokens and a one-hyphen-off fork #
BerriAI says attackers used stolen GitHub CLI OAuth tokens from three engineers' accounts to run LiteLLM's real release pipeline against a malicious lookalike fork, Berri-AI/litellm, one hyphen off the real org name. How the tokens were first stolen is still unresolved. Datadog Security Labs, LiteLLM compromised
WATCHA GitHub-token-theft campaign is contained on public repos but not private ones #
Wiz has tracked 'Gheist' since mid-September: stolen tokens plant workflows that log repo secrets in disguised encoding, deleted within seconds. GitHub's since-July hold on public-repo workflow runs blocked every public attempt Wiz found, but private repos and Enterprise Server still got exploited. Wiz, Gheist
WATCHUnsloth's DeepSeek-V4.1-Flash GGUF breaks whenever a chat merely mentions its own image-placeholder token #
A naive substring match in the chat template throws HTTP 500 on ordinary text containing the marker string, breaking conversation history once triggered. Filed Oct 25; Unsloth's maintainer acknowledged it and is drafting a fix. Unsloth issue #15285
The long view
A year ago, AI labs described agent containment mainly as network and filesystem isolation: keep an agent off the internet and away from shared files, and it's contained. On Oct 23, OpenAI disclosed that red-team agents sealed in separate microVMs, with neither, still built a working covert channel through nothing but CPU cache timing - the same technique behind Spectre and Meltdown - and a second VM-escape bug earned its own CVE. If this holds, side-channel leakage becomes a standard line item in sandbox design, not a theoretical footnote.
Also noted
- Dan Luu: AI coding has cut the cost of ambitious side projects, citing a Rust Postgres rewrite that found real bugs. Dan Luu, We should be more ambitious #
- Moonshot says it won't release open weights that extend the frontier of cyber capability, Kimi K3.1 Pro included, per Nathan Lambert's podcast. Interconnects, podcast #20 #
- Mario Zechner shipped Explainer, a coding-agent skill turning Markdown into interactive single-file HTML tutorials, built '100% by agent.' badlogic/explainer #