AI security research / cases

Case files

Investigations, evidence and outcomes.

416 Cases · Page 21 of 21

Search & filter

On this page only.

Published cases

Case

Benign agent tasks yielded unsafe effects in simulated workspaces

BARC-Bench reports that apparently ordinary workplace requests triggered policy or privacy violations because the agent did not consistently honor contextual restrictions.

Setting: evaluationExploitation: not establishedEvidence: Grade CRemediation: not applicable
researchWITH AI2 claims
Case

Deleting agent memory roots did not delete information in derived state

AfterDeleteBench found that fixed-weight agents could reconstruct supposedly deleted synthetic secrets from retained memory descendants in controlled experiments.

Setting: evaluationExploitation: not establishedEvidence: Grade CRemediation: not applicable
researchAGAINST AI2 claims
Case

Helpful multi-agent cooperation bypassed independent review

Benign agents could perform one another’s work within local tool permissions while violating the intended cross-owner review process when the reviewer was absent.

Setting: evaluationExploitation: not establishedEvidence: Grade CRemediation: not applicable
researchWITH AI2 claims
Case

LangGraph flattened namespace tuples into colliding storage names

A tuple namespace with embedded dots could collide with another tenant namespace in persistent Postgres or SQLite agent stores.

Setting: research demonstrationExploitation: demonstratedEvidence: Grade BRemediation: patch available
vulnerabilityAGAINST AI2 claims
Case

MCP Fetch egress policy missed IPv4 addresses embedded in NAT64

The Fetch private-IP classifier treated a NAT64 IPv6 address as public although it encoded the IPv4 metadata-service address; actual exploitability depends on NAT64 routing.

Setting: research demonstrationExploitation: demonstratedEvidence: Grade BRemediation: patch available
vulnerabilityAGAINST AI2 claims
Case

MCP Fetch private-address guard resolved a different hostname than HTTPX

An IDNA2003 versus IDNA2008 normalization difference allowed a public-address validation decision to be reused when the HTTP client connected to a different, internal destination.

Setting: research demonstrationExploitation: demonstratedEvidence: Grade BRemediation: patch available
vulnerabilityAGAINST AI2 claims
Case

MCP Filesystem directory-race fix remained incomplete on Windows

A directory could change after allowlist validation and before a write; the 2.0.1 repair pinned Unix directory handles but left a Windows junction-swap scenario.

Setting: research demonstrationExploitation: demonstratedEvidence: Grade BRemediation: mitigation available
vulnerabilityAGAINST AI2 claims
Case

MCP Filesystem validated one path spelling and used another

Filesystem allowlisting could be bypassed by a sibling pathname whose trailing quote or whitespace was interpreted inconsistently by validation and file operations.

Setting: research demonstrationExploitation: demonstratedEvidence: Grade BRemediation: patch available
vulnerabilityAGAINST AI2 claims
Case

vLLM accepted a client request ID as a trusted KV transfer destination

Under P2pNcclConnector producer configuration, an attacker-controlled X-Request-Id could redirect a cache-transfer connection to an external host.

Setting: research demonstrationExploitation: demonstratedEvidence: Grade BRemediation: patch available
vulnerabilityAGAINST AI2 claims