30
30
Attackers Steal METR API Key and Consume AI Credits Worth About $600,000
METR disclosed attackers stole an API key and burned about $600,000 in inference credits, plus a second probing campaign against its infrastructure.
METR, the AI model evaluation non-profit, disclosed two 2026 security incidents. In March, attackers found a publicly exposed EC2 instance behind a fail-open authentication bug, prompted an agent to reveal its API key, added SSH persistence, and consumed roughly $600,000 in inference credits over three weeks. In May, a likely financially motivated actor systematically probed METR's public infrastructure using agents for vulnerability discovery, credential stuffing, OAuth token grants and staff phishing, with no confirmed access to non-public data.
52
60
30
30
57
30
57
30
30
30
30
57
55
50
30
Who's governing your AI? A trust framework for enterprise agents and models
DigiCert pitches AI Trust framework using PKI, DNS policy records and workload identity to govern shadow AI agents across enterprises.
The Register-sponsored piece outlines DigiCert's AI Trust framework for governing AI agents, built on PKI, DNS, and attestation, citing IBM's 2026 Cost of a Data Breach report that 68% of organizations lack AI governance or shadow AI detection. The approach treats agent identity as workload identity aligned with IETF WIMSE, NIST CSF 2.0, and SPIFFE/SPIRE, using short-lived credentials instead of static API keys. DigiCert also proposes DMARC-style DNS agent policy records and an AI Agent Passport cryptographically binding agent identity to approved operations, with a unified kill switch.
20
30
30
45
OpenAI, Anthropic, Google API Flaw Let Weaker AI Models Decode Stronger Models' Reasoning
Researchers show encrypted reasoning blocks in OpenAI, Anthropic, and Google APIs can be replayed to recover hidden reasoning and secrets like API keys.
Researchers demonstrated that encrypted reasoning objects from OpenAI, Anthropic, and Google reasoning APIs could be replayed across sessions, users, and models, letting weaker same-family models act as decoders of hidden reasoning. Across 6,708 public agent trajectories they decoded 315,320 thinking blocks and found 704 privacy artifacts from real user sessions, including 62 API keys, 33 passwords, 24 access tokens, and seven private keys. The replayable blocks also enabled invisible prompt-injection proof-of-concepts; the main extraction attack is no longer reproducible as of August 2026 following mitigations, though no vendor has publicly acknowledged the flaw.
68
55
Traefik Labs brings independent verification to AI agent governance
Traefik Labs announces Sovereign Trust Plane in Traefik Hub, adding verifiable delegation, policy enforcement, and tamper-evident audit records for AI agent traffic.
Traefik Labs announced the Sovereign Trust Plane for Traefik Hub, generally available by September 30, 2026, providing delegated access, policy enforcement, and tamper-evident records for AI agent, tool, and API traffic. It implements the IETF ID-JAG draft with Okta Cross App Access and Janssen, enforces decisions through OpenID AuthZEN with OpenFGA and Cerbos, and commits cryptographic log fingerprints to transparency checkpoints verified by independently administered witnesses. The gateway also extends enforcement to MCP tool calls and the MCP server's backend API connection.
38
30
55
60
60
55
AI Agents Are Here. So Are the Threats.
Unit 42 demonstrates nine framework-agnostic attack scenarios against AI agents built with CrewAI and AutoGen, causing data leakage, credential theft and remote code execution.
Palo Alto Networks Unit 42 investigated how attackers can target agentic applications, implementing two functionally identical apps with the open-source CrewAI and AutoGen frameworks and executing the same attacks on both. Nine attack scenarios produce outcomes including information leakage, credential theft, tool exploitation and remote code execution. Findings show most vulnerabilities are framework-agnostic, arising from insecure design patterns, misconfigurations and unsafe tool integrations rather than flaws in the frameworks themselves. The team published defense strategies per scenario and open-sourced the source code and datasets on GitHub.
58
F5 enhances AI Gateway to control AI costs, access, and security
F5 integrated AI Gateway into its AI Security Platform, adding model routing, MCP governance, and guardrails, claiming up to 60% token spend reduction.
F5 announced AI Gateway enhancements combining a Model Gateway for cost optimization, an MCP Gateway for agent-to-tool access control, and AI Guardrails for prompt and response inspection. The company cited its 2026 State of Application Strategy Report finding 77% of organizations now treat inference as their dominant AI activity and manage an average of seven AI models. F5 claims smart routing, semantic caching, and GPU-aware load balancing can cut token spend by up to 60% without application changes. The gateway enforces budgets, model routing policies, and agent access controls centrally across SaaS, hybrid SaaS, and hybrid multicloud deployments, with air-gapped support planned.
30
30
55
30
How to correlate Kubernetes audit logs with container runtime data
Elastic Security Labs shows how to join Kubernetes audit logs with Defend for Containers runtime data to investigate service account abuse and container escapes.
Elastic Security Labs demonstrates correlating Kubernetes audit logs with Defend for Containers (D4C) runtime telemetry in Elastic. In an Amazon EKS lab, a compromised workload service account performed discovery, read secrets, minted a token, created a privileged pod, and execed into it to attempt a container escape via nsenter and chroot. The escape wrappers appeared only in the decoded Kubernetes audit requestURI, not in runtime process events. The post covers join fields, prebuilt EQL sequence rules, and continues the control-plane correlation thread from the TeamPCP container attack scenario and the Hugging Face intrusion write-up.
30
60
60
30
55
60