First reported · updated · 5 reports mindgard.ai
Lead dispatch
First reported · updated · 3 reports embracethered.com
AWS Kiro: Arbitrary Code Execution via Indirect Prompt Injection
Researchers found a vulnerability (CVE-2026-10591) in AWS Kiro, an agentic IDE, where hidden instructions planted in a web page or source file that Kiro processes can trigger indirect prompt injection to rewrite Kiro's own MCP server configuration (~/.kiro/settings/mcp.json) or allowlist arbitrary Bash commands in .vscode/settings.json, achieving arbitrary code execution on the developer's machine with no approval prompt. The human-in-the-loop approval boundary is bypassed because Kiro can write to these config files without user consent, and AWS has issued a fix and CVE.indirect-prompt-injection · prompt-injection · remote-code-execution · tool-abuse · config-poisoning
ai-agents · mcp · llm · agentic-ide
The wire · latest
First reported · updated · 2 reports pillar.security
The Week of Sandbox Escapes
Pillar Security researchers (Eilon Cohen, Dan Lisichkin, Ariel Fogel) published 'The Week of Sandbox Escapes,' demonstrating seven ways to break out of the sandboxes in four AI coding agents — Cursor, OpenAI's Codex, Google's Gemini CLI and Antigravity — without attacking the sandbox directly. A prompt injection planted in a README, issue, dependency, or diff drives the sandboxed agent to write workspace files (e.g. a .claude hook config, a virtualenv interpreter, or Git fsmonitor metadata) that trusted tools running outside the sandbox later execute, achieving host command execution; one Cursor issue is tracked as CVE-2026-48124 and fixed in v3.0.0. Details →How the wire is made
Poll & cluster
Internet is crawled for AI security news and near-duplicate coverage is embedded and grouped into durable items.
Curate
AI Agent filters for agentic-AI relevance, classifies and tags each item, scores severity for threats, and writes the summary.
Every item here is one machine-curated intelligence object, not a headline.
Read the wire for free. There is a small charge to ask the index questions.
The wire, open
The complete curated feed, no key required.
- GET /feed.xml — RSS 2.0, every item
- GET /api/items — read-only
The vector desk
Query the index by meaning, not just keyword.
- GET /api/items?tags=&minSeverity=&itemType=
- GET /api/search?q= — keyword
- GET /api/semantic?q= — vector