CVE-2026-54519: vmDeshpande ai-agent-automation · Missing Authorization
Affects vmDeshpande ai-agent-automationSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 0.9.1 soon.
Data as of 2 Nov 2026, 10:58 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.9.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.
What to do
Upgrade ai-agent-automation and vmdeshpande/ai-agent-automation to 0.9.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| vmDeshpandeai-agent-automation | Affected
| Fixed in
|
GitHubvmdeshpande/ai-agent-automationpkg:github/vmdeshpande/ai-agent-automationOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in vmDeshpande ai-agent-automation version 0.9.1. Users should upgrade to version 0.9.1 or later to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.
Description
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.