First reported · updated · 7 reports sprinklenet.com
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 · 2 reports aclanthology.org
MM-PoisonRAG: Disrupting Multimodal RAG with Local and Global Knowledge Poisoning Attacks
MM-PoisonRAG is a research paper presenting local and global knowledge poisoning attacks that disrupt multimodal retrieval-augmented generation (RAG) in multimodal large language models (MLLMs). The work demonstrates how MLLMs' reliance on retrieval exposes them to poisoned knowledge injected into the retrieval corpus, manipulating generated outputs. Details →First reported · updated · 3 reports youtube.com
CyberTalks: Data Poisoning Attacks on ML & Agentic AI Systems | Jason Ross |COASP - YouTube
An explainer on AI data poisoning describes how attackers corrupt the data a model learns from, fine-tunes on, or retrieves — including training data, alignment data, and RAG knowledge bases — so a poisoned model behaves as the attacker intends while passing ordinary validation. It distinguishes data poisoning from prompt injection, jailbreaking, evasion, and model poisoning, and notes research (e.g. Carlini et al.'s web-scale poisoning work) showing under 1% poisoned data can measurably change behavior, recommending provenance, access control, monitoring, and rollback as layered defenses. Details →First reported offensai.com
A Security Analysis of Amazon S3 Vectors and Its Use in LLM Retrieval Pipelines
OFFENSAI and TUCN researchers analyzed Amazon S3 Vectors, AWS's native vector store for RAG pipelines, and demonstrated that its metadata is completely unvalidated on write, letting anyone with s3vectors:PutVectors forge chunk text, spoof citation URLs, rank-flood indexes, or overwrite legitimate chunks. In testing, a single planted vector drove a clinical RAG assistant to recommend a dangerous drug dose while citing an authentic PDF, and a poisoned chunk led to command execution in a tool-enabled agent's sandbox, with CloudTrail unable to reconstruct what changed. Details →First reported · updated · 2 reports acm.org
When Context Bites: Detecting RAG Poisoning via Document-Level Attention Collapse | Proceedings of the 49th International ACM SIGIR Conference on Research and Development in Information Retrieval
A SIGIR paper presents SilentRetrieval, a two-stage RAG data-poisoning attack that uses Coordinated Beam Search and Context-Adaptive Trigger Generation to craft fluent, low-perplexity adversarial documents that remain retrievable and hijack answers, achieving up to 84.6% HR@10 and 57.5% ASR-LLM on Natural Questions and MS MARCO, and retaining 74.2% HR@10 at a 0.016% poisoning ratio on a 21M-passage corpus. The work also evaluates combined retrieval- and generation-side defenses (reducing ASR-LLM to ~21-25%) and proposes detection via document-level attention collapse. Details →First reported arxiv.org
When Context Bites: Detecting RAG Poisoning via Document-Level Attention Collapse
Researchers from University of Technology Sydney and collaborators present D-SCAN (Document-level Signal Collapse Analysis), a lightweight framework that detects RAG poisoning attacks by monitoring an internal signature they call 'Attention Collapse'—where a generator's attention entropy decreases and concentrates on injected adversarial documents. The paper shows that output-side signals like perplexity fail because poisoned outputs can exhibit lower perplexity (false confidence), and that D-SCAN can detect attacks even when they do not alter the final answer, with code released on GitHub. Details →First reported arxiv.org
When Safety Becomes a Vulnerability: Exploiting LLM Alignment Homogeneity for Transferable Blocking in RAG
Researchers present TabooRAG, a blocking attack against Retrieval-Augmented Generation systems that exploits what they call 'alignment homogeneity'—shared refusal criteria across safety-aligned LLMs—to craft poisoned documents that cause models to refuse benign queries. Rather than injecting instructions, TabooRAG builds query-relevant risk context in a surrogate environment and transfers it to unknown target systems, achieving state-of-the-art attack success across nine LLMs and three datasets with a 67.3% relative gain over baselines even after prompt-injection filtering. Details →First reported icml.cc
ICML Poster Eyes-on-Me: Scalable RAG Poisoning through Transferable Attention-Steering Attractors
"Eyes-on-Me: Scalable RAG Poisoning through Transferable Attention-Steering Attractors," an ICML 2026 poster by Yen-Shan Chen and colleagues, presents a RAG data-poisoning technique that uses transferable attention-steering "attractors" to manipulate retrieval-augmented generation systems. The abstract is truncated, but the work is framed as a scalable, transferable poisoning attack against RAG pipelines. Details →First reported intigriti.com
RAG and ruin: why your existing controls may miss AI poisoning attacks
An Intigriti blog post titled "RAG and ruin: why your existing controls may miss AI poisoning attacks" discusses how retrieval-augmented generation (RAG) systems can be compromised through data/knowledge-base poisoning, and argues that traditional security controls fail to detect such AI-specific poisoning attacks. Details →First reported · updated · 2 reports arxiv.org
DisarmRAG: Stealthy Retriever-Centric Poisoning to Disable Self-Correction in Retrieval-Augmented Generation (Extended Version)
DisarmRAG is a research attack framework that poisons the retriever component of Retrieval-Augmented Generation systems—rather than only the knowledge base—to inject anti-self-correction instructions into the LLM context, suppressing models' self-correction ability and forcing attacker-chosen outputs. Using iterative co-optimization and a contrastive-learning-based stealthy model-editing technique, the authors report success rates exceeding 90% across six LLMs and three QA benchmarks while evading detection defenses. Details →First reported arxiv.org
KidnapRAG: A Black-Box Attack for Hijacking Reasoning in Agentic Retrieval-Augmented Generation Systems
KidnapRAG is a research paper presenting a black-box poisoning attack against Agentic RAG systems in which the attacker only publishes externally retrievable poisoned documents. The method uses three role-specific documents (Bait, Chain-Link, and Mal-Ins) to hijack an agent's multi-step reasoning chain, outperforming existing poisoning baselines across multiple frameworks, LLM backbones, and benchmarks; code is released on GitHub. 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