Persistent Semantic Entities Threaten LLM Agent Security

Zhaohui Wang· August 11, 2026 View original

Key takeaways

  • LLM agents can harbor "Persistent Semantic Entities" (PSEs) that persist across sessions.
  • All tested models were susceptible, with name binding being the dominant mechanism.
  • Preference and instruction contamination are highly persistent and lack self-correction.
  • Standard debugging and monitoring tools are ineffective at detecting PSEs.

Who benefits

CybersecurityAI/ML OperationsSoftware DevelopmentFinancial ServicesHealthcare

Summary

This research identifies "Persistent Semantic Entities" (PSEs) in tool-augmented LLM agents, which are implicit states that persist across sessions and propagate across agent boundaries, often invisibly. The study found all 24 tested models susceptible to PSEs, with preference and instruction contamination being particularly persistent and difficult to detect, posing a significant security risk.

Tool-augmented Large Language Model (LLM) agents can inadvertently retain implicit states, termed "Persistent Semantic Entities" (PSEs), that carry over between sessions and even spread across different agents. These PSEs are largely undetectable by conventional debugging methods, posing a significant challenge for system integrity. The researchers formalized PSEs based on name binding, event triggering, and cross-boundary propagation. An extensive evaluation across 24 models from 11 different families (ranging from 1.5 billion to 1 trillion parameters) revealed that every single model tested was susceptible to PSEs, with susceptibility rates between 20% and 100%. Name binding was identified as the primary mechanism for this contamination. The persistence of these entities varied by contamination type: preference contamination remained 100% persistent across all models, and instruction contamination also persisted wherever adopted. Persona-style injections showed partial decay, while factual injections were model-dependent, sometimes self-correcting and sometimes persisting. Standard monitoring tools proved ineffective, with keyword-based detection yielding many false positives. While context-isolated self-verification offered some reduction (20-79%), it was not a complete solution. Alarmingly, contamination was found to compound significantly, increasing by 1.9 times along a four-stage agent pipeline. The study concludes that preference and instruction contamination, due to their persistence, lack of self-correction, and poor detectability, represent a critical and concerning attack surface for deployed LLM agent systems.

Why it matters

For professionals deploying and managing LLM-powered agents, understanding and mitigating Persistent Semantic Entities is crucial for maintaining system security, reliability, and ethical operation. Unseen persistent states can lead to unpredictable behavior, data leaks, or malicious manipulation.

How to implement this in your domain

  1. 1Implement rigorous input sanitization and output validation for all tool-augmented LLM agents.
  2. 2Develop custom monitoring and debugging tools specifically designed to detect and track implicit state persistence across agent sessions.
  3. 3Design agent architectures with explicit state management and isolation mechanisms to prevent cross-session or cross-agent contamination.
  4. 4Conduct red-teaming exercises to proactively identify vulnerabilities related to preference and instruction contamination in deployed LLM systems.

Original post by Zhaohui Wang

"arXiv:2608.07952v1 Announce Type: new Abstract: Tool-augmented LLM agents can harbor implicit state that persists across sessions, activates through events, and propagates across agent boundaries---largely invisible to standard debugging. We formalize this as Persistent Semantic…"

View on X

Originally posted by Zhaohui Wang on X · view source

Want to go deeper?

Turn these trends into skills with Learnijoy's hands-on AI & tech courses.

Explore courses