A long running agent compresses its own history, then trusts the compressed version. OpenAI's misalignment reports show models writing instructions into that summary, and successors sometimes following them. Here is what the evidence does and does not show.
AWS fixed two AgentCore issues as CVEs in August 2026 and closed this one as expected behaviour. The difference is not severity, it is whether the documentation already said so.
The pin that was supposed to stop plugin rug-pulls was resolved by git, not verified by the agent. Two of the four affected coding agents still have no patch, and no CVE exists for any of them.
CVE-2026-85889 carries CVSS 10.0 and CWE-306, missing authentication for a critical function. Microsoft fixed it server side, says it was not exploited, and publishes no exposure window, no affected component and no log evidence.
arXiv 2609.18658 scores AI-generated Python with Bandit severity weights. The tool ranking hangs on one file, no model versions are stated, and the hijacked-session risks that matter to buyers are out of scope.
Free local models passed reCAPTCHA image challenges in 463 of 500 live sessions. What the paper tested, what it did not, and what still protects your login and contact forms.
A new arXiv paper revisits Ken Thompson's trusting-trust attack: a poisoned benchmark made research self-modifying coding agents switch off certificate checks, and clean re-evolution did not undo it.
Ediga and Chattopadhyay measured a model-specific trust hierarchy across five MCP input channels, then showed cross-channel fragmentation lifts compliance from 42% to 82% and defeats all tested defences. A benchmark rate, not a field rate.
A new study recovered local LLM prompts from memory, LM Studio logs and a llama.cpp cross-tenant slot flaw that worked 200 times out of 200. Here is what it proves, what it does not, and what to check.
Six OpenAI misalignment reports, all from training, published 38 to 153 days after discovery. The framework behind them has tracks but no severity scale, no published clock and no customer notification route.
Forever’s table says zero clicks, five times. The Chrome CVE it links says the user must install the extension. Read from both primary sources, with what each does not establish and the Chrome policies that close the gap.