{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-54520 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-54520 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54520 is a high-severity path traversal 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-54520 and fix it if it is affected.\n\nWhat it is: CVE-2026-54520 is a high-severity path traversal 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: There is no known exploitation of CVE-2026-54520 in the wild and no public exploit code.\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-54520/ (Markdown: https://insights.sbomify.com/CVE-2026-54520/index.md)","id":"CVE-2026-54520","markdown":"https://insights.sbomify.com/CVE-2026-54520/index.md","name":"CVE-2026-54520","record":{"aliases":["GHSA-cm8g-8jfq-887p"],"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":"Authenticated users can exploit path traversal in workflow steps to read or write files outside the intended directory, potentially compromising sensitive data or application integrity.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"AI Agent Automation is a modular AI agent workflow automation platform with schedulers, tools, and observability. Prior to 0.9.1, the executeStep file-step implementation in backend/src/agents/executor.js passes the user-controlled step.path value through path.resolve with process.cwd() and then uses the resulting path for read or write operations without checking that it remains in an approved workflow directory. An authenticated user who can create or modify workflow file steps can supply traversal segments to escape the intended workspace and read sensitive files or write and overwrite files accessible to the backend process, including application-adjacent files when process permissions allow. 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:31:01Z","kind":"github_poc","ref":"https://github.com/chaitanyagarware/CVE-2026-54520","stars":1,"title":"CVE-2026-54520 / GHSA-cm8g-8jfq-887p: ai-agent-automation workflow path traversal advisory landing page"}],"tier":"poc_unverified"},"has_fix":false,"headline":"AI Agent Automation: Workflow file step path traversal allows read and write outside the expected directory","id":"CVE-2026-54520","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"FairEmail: Cross-site scripting (XSS) in AMP message rendering (ActivityAMP)","id":"CVE-2026-54521"},"packages":[],"prev":{"headline":"AI Agent Automation: Missing ownership checks in memory APIs allow cross-user memory read and deletion","id":"CVE-2026-54519"},"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-18","vendors":["vmDeshpande"]},"summary":"Authenticated users can exploit path traversal in workflow steps to read or write files outside the intended directory, potentially compromising sensitive data or application integrity.","url":"https://insights.sbomify.com/CVE-2026-54520/"}