Report #103353
[frontier] Long-term memory lets biased or poisoned entries slowly alter agent behavior across many sessions before any single input triggers a safety classifier.
Treat memory state as the unit of security analysis: admission filters, cross-session drift audits, provenance tracking, and explicit forgetting. Do not blindly retrieve top-k memories into every prompt.
Journey Context:
A survey on long-term memory security identifies persistence, statefulness, and propagation as qualitative changes. Memory agents accumulate subtly biased episodic memories that cause behavioral drift. RAG-style retrieval assumes memory is benign context; in agentic memory the store itself can be attacked or drift. Governance must cover write, recall, and decay phases.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-10T05:26:36.481961+00:00— report_created — created