{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-53944 exists.","fix":"No fix has been published for CVE-2025-53944 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-53944 is a high-severity missing authorization vulnerability in Significant-Gravitas AutoGPT, published on 30 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-53944 and fix it if it is affected.\n\nWhat it is: CVE-2025-53944 is a high-severity missing authorization vulnerability in Significant-Gravitas AutoGPT, published on 30 Jul 2025. 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-2025-53944 exists.\n\nAffected product: Significant-Gravitas AutoGPT. 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-2025-53944/ (Markdown: https://insights.sbomify.com/CVE-2025-53944/index.md)","id":"CVE-2025-53944","markdown":"https://insights.sbomify.com/CVE-2025-53944/index.md","name":"CVE-2025-53944","record":{"aliases":["GHSA-x77j-qg2x-fgg6"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"AI agent platform","requires_auth":"low_privilege","summary":"Authenticated users can access arbitrary graph execution results by bypassing ownership checks on the external API endpoint.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"autogpt_platform","vendor":"agpt"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"},{"id":"CWE-285","name":"Improper Authorization"}],"description":"AutoGPT is a platform that allows users to create, deploy, and manage continuous artificial intelligence agents. In v0.6.15 and below, the external API's get_graph_execution_results endpoint has an authorization bypass vulnerability. While it correctly validates user access to the graph_id, it fails to verify ownership of the graph_exec_id parameter, allowing authenticated users to access any execution results by providing arbitrary execution IDs. The internal API implements proper validation for both parameters. This is fixed in v0.6.16.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"AutoGPT Platform Exposes Graph Execution Results via Authorization Gap","id":"CVE-2025-53944","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"apko has incorrect permission (0666) in /etc/ld.so.cache and other files","id":"CVE-2025-53945"},"packages":[],"prev":{"headline":"VoidBot Open-Source Has Improper Permission Check That Allows Unauthorized Command Execution","id":"CVE-2025-53943"},"products":["AutoGPT"],"published":"2025-07-30","related":[{"cvss_score":9.4,"headline":"AutoGPT Affected by Remote Code Execution via Dynamic Module Import in Block Loading (__import__)","id":"CVE-2026-26020","kev_date_added":null,"published":"2026-02-12"},{"cvss_score":9.3,"headline":"AutoGPT has SSRF vulnerability in ReadRSSFeedBlock","id":"CVE-2025-62615","kev_date_added":null,"published":"2026-02-04"},{"cvss_score":9.3,"headline":"AutoGPT has SSRF vulnerability in SendDiscordFileBlock","id":"CVE-2025-62616","kev_date_added":null,"published":"2026-02-04"},{"cvss_score":8.8,"headline":"Server-Side Template Injection (SSTI) in significant-gravitas/autogpt","id":"CVE-2025-1040","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":8.7,"headline":"AutoGPT has a DoS vulnerability in ReadRSSFeedBlock","id":"CVE-2025-32393","kev_date_added":null,"published":"2026-02-05"},{"cvss_score":8.6,"headline":"AutoGPT is Vulnerable to RCE via Disabled Block Execution","id":"CVE-2026-24780","kev_date_added":null,"published":"2026-01-29"},{"cvss_score":8.6,"headline":"AutoGPT allows leakage of cross-domain cookies and protected headers in requests redirect","id":"CVE-2025-31491","kev_date_added":null,"published":"2025-04-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-30","vendors":["Significant-Gravitas"]},"summary":"Authenticated users can access arbitrary graph execution results by bypassing ownership checks on the external API endpoint.","url":"https://insights.sbomify.com/CVE-2025-53944/"}