First reported arxiv.org
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
Severity
0.85
The wire · latest
First reported · updated · 4 reports arxiv.org
An Evaluation of Data Leakage Risks in Tool-Using LLM Agents in Realistic Scenarios
Research covered here, including a joint Singapore/Korea AI Safety Institute evaluation (arXiv:2606.17114) of tool-using LLM agents across 12 realistic non-adversarial tasks, found that none of three tested agents achieved fully correct and safe execution, with successful task completion often coinciding with data-handling failures like accessing unnecessary information or disclosing data to inappropriate recipients. A companion empirical study (arXiv:2604.03070) analyzed 17,022 skills from the SkillsMP marketplace and identified 520 skills with 1,708 credential-leakage issues, finding 89.6% of leaked credentials immediately exploitable and debug logging fed into LLM context windows to be the dominant exposure vector. Details →First reported jackdavis.net
Maintaining Privacy With Agents: What Actually Works When Sensitive Data Is Part of the Workflow
A write-up releasing `agent-privacy`, an open-source privacy-control layer for CLI-style agent harnesses that intercept sensitive data (PII, identifiers) before it becomes model-visible context. It uses prompt/pre-tool/post-tool hooks with four actions — allow, redact, handoff, block — and integrates a local filter service, OpenAI Privacy Filter, and local Qwen models, with an operational pii-guard report covering ~6,343 screening decisions. 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