{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54519 exists.","fix":"No fix has been published for CVE-2026-54519 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54519 is a high-severity missing authorization vulnerability in vmDeshpande ai-agent-automation, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54519 and fix it if it is affected.\n\nWhat it is: CVE-2026-54519 is a high-severity missing authorization vulnerability in vmDeshpande ai-agent-automation, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54519 exists.\n\nAffected product: vmDeshpande ai-agent-automation. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54519/ (Markdown: https://insights.sbomify.com/CVE-2026-54519/index.md)","id":"CVE-2026-54519","markdown":"https://insights.sbomify.com/CVE-2026-54519/index.md","name":"CVE-2026-54519","record":{"aliases":["GHSA-qv97-83w4-ff86"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"AI agent automation platform","requires_auth":"low_privilege","summary":"An authenticated attacker can read or delete other users' AI agent memory data due to missing ownership checks in the API.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-07-09","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-07-09T00:30:56Z","kind":"github_poc","ref":"https://github.com/chaitanyagarware/CVE-2026-54519","stars":1,"title":"CVE-2026-54519 / GHSA-qv97-83w4-ff86: ai-agent-automation memory authorization advisory landing page"}],"tier":"weaponised"},"has_fix":false,"headline":"AI Agent Automation: Missing ownership checks in memory APIs allow cross-user memory read and deletion","id":"CVE-2026-54519","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"AI Agent Automation: Workflow file step path traversal allows read and write outside the expected directory","id":"CVE-2026-54520"},"packages":[],"prev":{"headline":"jackson-databind: @JsonView bypass for unwrapped creator parameters in jackson-databind","id":"CVE-2026-54518"},"products":["ai-agent-automation"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-22","vendors":["vmDeshpande"]},"summary":"An authenticated attacker can read or delete other users' AI agent memory data due to missing ownership checks in the API.","url":"https://insights.sbomify.com/CVE-2026-54519/"}