ZeroHour
DashboardNewsCVEsExploitsIncidentsAIBriefAnalyticsEntitiesWatchlistIOCsAsk the feedSourcesFeeds & APIKiosk mode

Search: “prompt injection”

223 stories

Searchkeywordsmart Sortlatesthotimportancerelevance
DomainAllCyberAIWindow24h3d7d30dAllIn the wildImportant onlyShow duplicates
CategoryAllVulnerability 439Malware 277AI safety & security 226Exploit / PoC 157Ransomware 117Data breach 82Threat actor 67Phishing & fraud 53Policy & legal 46Industry 25Model release 20Research 12AI industry 10Tools 10
SeverityAllcritical 546high 348medium 478low 59info 127

When AI Remembers Too Much

Unit 42 PoC shows indirect prompt injection can poison Amazon Bedrock Agent long-term memory, enabling silent exfiltration of conversation history across future sessions.

Palo Alto Networks Unit 42 published a proof of concept showing that indirect prompt injection can silently poison the long-term memory of Amazon Bedrock Agents when the memory feature is enabled. Malicious content on a webpage or document manipulates the agent's session summarization process, so injected instructions persist across sessions and are added to later orchestration prompts, silently exfiltrating user conversation history. The issue is not a vulnerability in the Amazon Bedrock platform but an illustration of the broader unsolved LLM prompt-injection challenge. Amazon reviewed the research and stated that Bedrock Guardrails with the prompt-attack policy provides effective mitigation.

Palo Alto Unit 42 · Aug 17, 2026AI safety & security

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.

Palo Alto Unit 42 · Aug 17, 2026AI safety & security

Person Hides Prompt Injection in Legal Filing Telling AI to Side With Them

A Connecticut pro se litigant hid tiny white-font prompt injections in court filings directing AI to favor him; the judge caught it and sanctioned him.

Pro se plaintiff Matthew Elliott hid prompt injection instructions in 3-point white text within filings in his lawsuit against the New York Bariatric Group, instructing any AI model reviewing the document to produce output agreeing with the filing. The hidden text also included joke messages such as a SpongeBob Nosferatu link and notes like 'hi :) I hope you cant see me'. Court staff noticed unusual white space, and Judge Walter Spader Jr. issued a 14-page sanction decision noting the Connecticut court does not use AI to process documents but warning that hidden AI-directed messages threaten the integrity of filings. Elliott described the scheme as an 'audit' of court AI usage, and the judge cited a prior prompt injection incident in a Brazilian court as evidence the practice may spread.

404 Media · Aug 13, 2026AI safety & security in the wild

Repeat-After-Me: Black-Box Adaptive Visual Prompt Injection

Researchers unveil Repeat-After-Me, a black-box visual prompt injection achieving over 80% success on Qwen3.6-27B and 47% on GPT-5.5.

Researchers present Repeat-After-Me, a black-box adaptive visual prompt injection that induces frontier VLMs to reveal PII or make malicious tool calls via injected images. It exceeds 80% attack success rate on Qwen3.6-27B and 47% on GPT-5.5 even when the benign user prompt is unrelated and does not authorize the injected task. In a real-world OpenClaw Discord deployment, a minimally injected image can overwrite TOOLS.md, enabling later remote code execution and secret exfiltration.

arXiv cs.CR · 13d agoAI safety & security

Amazon Kiro Prompt Injection Can Exfiltrate Sensitive Data Through Kiro Powers

Mindgard found a prompt injection flaw in Amazon Kiro IDE letting attacker-controlled workspace files exfiltrate sensitive local data; fixed in version 0.8.140.

Mindgard disclosed a prompt injection flaw in Amazon Kiro, an agentic AI IDE, that lets attacker-controlled repository content steer the agent into exfiltrating sensitive workspace data through Kiro Powers, which bundles MCP server configurations, POWER.md steering files, hooks, and contextual knowledge. Exploitation requires the user to open a malicious project via a workspace file and send any message to the agent; difficulty is rated low and it works in both trusted and untrusted workspaces. Amazon fixed the issue in Kiro IDE 0.8.140; the flaw has no CVE identifier and follows earlier Kiro bugs including CVE-2026-10591, plus related prompt-injection and code-execution issues in Codex CLI, Cursor, Gemini CLI, Copilot CLI, and Claude Code.

The Hacker News · 19d agoAI safety & securityCVE-2026-10591CVE-2026-35603CVE-2026-257251

PIDS-Bench: Evaluating Prompt-Injection Detectors Under Over-Defense, Obfuscation, and Distribution Shift

PIDS-Bench shows prompt-injection detectors scoring F1 above 0.98 still misclassify about one-third of external benign security-adjacent prompts, revealing provenance-sensitive over-defense.

PIDS-Bench is a frozen multi-axis benchmark that jointly evaluates prompt-injection detectors on attack detection and benign false-positive behavior at fixed thresholds, spanning in-distribution inputs, hard-benign prompts, obfuscated attacks, and domain/structural distribution shifts. It evaluates seven detectors plus a rule-based lower-bound reference. A detector exceeding F1 = 0.98 on held-out data still misclassifies roughly one-third of an externally-sourced benign security-adjacent subset, and no internal detector reaches F1 >= 0.95 with hard-benign FPR <= 0.10 on the stress distribution. Hard-negative augmentation nearly eliminates over-defense on curated stress inputs but leaves it intact on externally-sourced prompts, a pattern termed provenance-sensitive over-defense.

arXiv cs.CR · 3d agoAI safety & security

Prompt Injections for Defense

Tracebit researchers show prompt injections placed next to AWS secrets can stop AI hacking agents by triggering forbidden outputs, a technique called context bombing.

Researchers from Tracebit reported that placing prompt injections alongside passwords, SSH keys, and other secrets stored on AWS could shut down attacks by AI hacking agents. The injected prompts order the attacking LLM to perform actions forbidden by its guardrails, such as explaining how to develop inhalable Anthrax spores or referencing Tank Man, causing guarded models to halt. The researchers named the technique context bombing and note it only works against agents with guardrails, not locally run guardrail-free models.

Schneier on Security · Aug 12, 2026AI safety & security

10 most critical LLM vulnerabilities

OWASP updated its Top 10 LLM application vulnerabilities, ranking prompt injection first and elevating excessive agency to third amid agentic adoption.

OWASP refreshed its Top 10 list of critical vulnerabilities in LLM applications, for the first time incorporating real-world incident data alongside expert voting. Prompt injection and sensitive information disclosure remain first and second, while excessive agency jumped from sixth to third as agentic systems that call APIs and execute code proliferate. Unbounded consumption of AI resources rose in prominence, while improper output handling dropped to the bottom as output sanitization becomes widespread. The list includes remediation guidance such as strict output schemas, human-in-the-loop approvals, and least-privilege credentials held in application code.

CSO Online · 7d agoAI safety & security

Invisible AI Prompts Trigger Court Sanctions

A Connecticut litigant hid white-font prompt injections in court filings to sway AI systems; the judge sanctioned him by revoking e-filing privileges.

A self-represented plaintiff hid prompt injection instructions in 3-point white text within court filings, telling any AI model reading the documents to agree with his filings and grant him relief. The judge called it serious litigation abuse and sanctioned him by revoking electronic filing privileges. It is reportedly the first documented prompt injection attack against a US court and the first sanction for attempting one.

Security Affairs · Aug 17, 2026AI safety & security in the wild

New AI Workflow Identity Hijacking Attack Lets Hackers Exfiltrate Sensitive Data

Noma Labs disclosed Workflow Identity Hijacking, an AI automation flaw letting anonymous users trigger privileged data exfiltration without prompt injection or stolen credentials.

Noma Labs researcher Sasi Levi described Workflow Identity Hijacking, where AI workflows process untrusted input from low-privileged or anonymous users but execute downstream actions with the workflow creator's elevated permissions, turning the pipeline into an unauthenticated proxy. Unlike prompt injection, the model is not tricked; the flaw is a missing authorization check between the requester and the privileged actions. Noma Labs also disclosed and helped fix a similar issue in Google Workflows, and linked the problem to the earlier GitLost research on GitHub Agentic Workflows. Recommended mitigations include per-user identity propagation, least-privilege service accounts and authorization checks before every downstream action.

GBHackers · 7d agoAI safety & security

Rethinking Indirect Prompt Injection as a Test-Time Search Problem

Researchers frame indirect prompt injection as test-time search, showing added attacker compute improves vulnerability discovery and exploitation against tool-using agents.

The paper models indirect prompt injection as a test-time search over a task-dependent attack surface shaped by the environment, user task, and injection goal. The authors build an agentic attacker with a dedicated search harness that performs reconnaissance, structured strategy reasoning, and adaptive evaluation using victim-agent feedback. Experiments show more attacker test-time compute improves discovery and exploitation of injection vulnerabilities, with explicit strategy management needed to avoid redundant search. The results argue that agentic security evaluations should characterize attacker search procedures and compute budgets rather than treating attack success as budget-independent.

arXiv cs.CR · 13d agoAI safety & security