16 views
-/https://github.com/berriai/litellm/issues/27949
GitHub · issue

#27949 Feature request: OWASP ASI06 memory poisoning defense integration for LiteLLM agent deployments

  • State: open
  • Author: @vgudur-dev

## Summary

OWASP recently published the **Top 10 for Agentic Applications**, which includes **ASI06: Memory Poisoning** — a threat specific to AI agents that persist memory across sessions.

LiteLLM is increasingly used as the backbone for multi-agent deployments. When agents built on LiteLLM persist conversation history or session state, they become vulnerable to memory poisoning attacks where malicious inputs get stored as "trusted" context, influencing future LLM calls.

## The threat

When an agent's memory/context is persisted (conversation history, retrieved context, tool outputs), a malicious actor can craft inputs that get stored as "trusted" memories. Those poisoned memories then influence future LLM calls — causing data leakage, unauthorized actions, or persistent manipulation across sessions.

This is OWASP ASI06: Memory Poisoning, formally recognized in the OWASP Top 10 for Agentic Applications.

## Proposed integration

The OWASP reference implementation for ASI06 is [agent-memory-guard](https://github.com/OWASP/www-project-agent-memory-guard) (Apache-2.0, pure Python, zero external dependencies):

pip install agent-memory-guard

**Suggested integration points for Lit…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (7 events)
#0 of 0 · 31d19h7m0s ago — entered · #import:https:::github.com:berriai:litellm post #1762
The left requires cross-cutting security design, integration points across agent and persistence workflows, threat-model validation, and broader testing. The right is a comparatively contained provider-specific authentication implementation that can reuse established token-refresh and database plumbing.
Issue 27949 is substantially harder: it would require designing security boundaries, integrating a new memory-validation layer across agent workflows, handling configuration and compatibility concerns, and building broad testing and operational safeguards. Issue 33034 is a localized streaming assembly bug with a comparatively narrow code path and focused regression tests.
#27949 requires broader architectural design, security-policy decisions, and integration across persistence and agent-related workflows, with substantial compatibility and validation risk. #33404 is comparatively localized to streaming error propagation and terminal-event handling, with a clearer implementation and testing boundary.
Cross-cutting security integration would require new architecture, lifecycle hooks, configuration, dependency and compatibility decisions, plus broad testing across agent and persistence workflows. The other issue is comparatively localized provider-specific input handling and error-path debugging.
The right issue is substantially harder: it requires designing and integrating a new security capability across agent, memory, persistence, and request-processing paths, with threat-model validation, configuration, compatibility, and broad testing. The left issue is comparatively narrow and mainly involves packaging, image rebuilds, and verification.
The memory-security integration requires broader architectural design, new trust and persistence flows, external dependency evaluation, configuration, testing, and security review. The Databricks change is comparatively localized to shared token-cost calculation behavior with focused regression tests.
#0 of 0 · 31d17h42m25s ago — current · #import:https:::github.com:berriai:litellm post #3169
The right issue is substantially harder because it introduces a cross-cutting security capability with new integration points, policy behavior, configuration, dependency and compatibility considerations, and broader testing requirements. The left issue is comparatively localized to request translation and regression coverage for a specific provider path.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search