CVE-2026-54519
HighCVSS 8.8Exploitation Probability (EPSS)
Low risk41th percentile - higher than 41% of all known CVEs
Summary
In AI Agent Automation prior to 0.9.1, listMemories, deleteMemory, and clearAgentMemory use caller-supplied identifiers without verifying record ownership. An authenticated attacker who knows a victim's identifiers can read, delete, or clear the victim's agent memory data.
Risk Assessment
Broken tenant isolation leads to unauthorized disclosure of data (conversation history, agent context, task data, embeddings) and data loss. This may result in information leakage and compliance issues.
Recommendation
Upgrade AI Agent Automation to version 0.9.1 or later. Verify that access control for memory resources is properly enforced.
Other vulnerabilities in AI Agent Automation
Original NVD description (English source)
AI Agent Automation is a modular AI agent workflow automation platform with schedulers, tools, and observability. Prior to 0.9.1, backend/src/controllers/memory.controller.js authenticates requests but listMemories, deleteMemory, and clearAgentMemory use a caller-supplied agentId or memory _id without verifying through the related Agent that the record belongs to req.user. An authenticated attacker who knows or obtains another user's identifiers can read victim AgentMemory content, including conversation history, agent context, task data, embeddings, and metadata, delete an individual victim memory, or clear all memory belonging to a victim agent. This breaks tenant isolation and causes unauthorized disclosure and data loss. This issue is fixed in version 0.9.1.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS

