{"answers":{"affected":"3 open source packages ship an affected version, including composio-core. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-8953 exists.","fix":"Upgrade composio-core to 0.5.43 or later.","what":"CVE-2024-8953 is a high-severity code injection vulnerability in composiohq/composio, published on 20 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-8953 and fix it if it is affected.\n\nWhat it is: CVE-2024-8953 is a high-severity code injection vulnerability in composiohq/composio, published on 20 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-8953 exists.\n\nAffected packages and fixed versions:\n- composio-core (PyPI): affected all versions; fixed in 0.5.43\n- composio-core (PyPI): affected all versions; fixed in 0.5.43\n- composio-core (PyPI): affected all versions; fixed in 0.5.43\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-2024-8953/ (Markdown: https://insights.sbomify.com/CVE-2024-8953/index.md)","id":"CVE-2024-8953","markdown":"https://insights.sbomify.com/CVE-2024-8953/index.md","name":"CVE-2024-8953","record":{"aliases":["GHSA-5xg7-5662-8x7j","PYSEC-2026-1264"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Python library","requires_auth":"high_privilege","summary":"Attackers can execute arbitrary code via the mathematical_calculator endpoint due to unsafe eval usage in the composio library.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"composio","vendor":"composio"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-913","name":"Improper Control of Dynamically-Managed Code Resources"},{"id":"CWE-627","name":"Dynamic Variable Evaluation"}],"description":"In composiohq/composio version 0.4.3, the mathematical_calculator endpoint uses the unsafe eval() function to perform mathematical operations. This can lead to arbitrary code execution if untrusted input is passed to the eval() function.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Unsafe eval usage in composiohq/composio","id":"CVE-2024-8953","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"code_injection","year":"2024"},"n_packages":3,"n_references":1,"next":{"headline":"Authentication Bypass in composiohq/composio","id":"CVE-2024-8954"},"packages":[{"ecosystem":"PyPI","fixed":["0.5.43"],"introduced":["0"],"last_affected":[],"package":"composio-core","purl":null,"source":"GHSA-5xg7-5662-8x7j"},{"ecosystem":"PyPI","fixed":["0.5.43"],"introduced":["0"],"last_affected":[],"package":"composio-core","purl":"pkg:pypi/composio-core","source":"GHSA-5xg7-5662-8x7j"},{"ecosystem":"PyPI","fixed":["0.5.43"],"introduced":["0"],"last_affected":[],"package":"composio-core","purl":"pkg:pypi/composio-core","source":"PYSEC-2026-1264"}],"prev":{"headline":"SSRF in composiohq/composio","id":"CVE-2024-8952"},"products":["composiohq/composio"],"published":"2025-03-20","related":[{"cvss_score":9.8,"headline":"Authentication Bypass in composiohq/composio","id":"CVE-2024-8954","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":7.5,"headline":"ComposioHQ has a directory traversal vulnerability","id":"CVE-2025-56427","kev_date_added":null,"published":"2025-12-04"},{"cvss_score":7.2,"headline":"Unrestricted File Write and Read in composiohq/composio","id":"CVE-2024-8958","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":6.8,"headline":"SSRF in composiohq/composio","id":"CVE-2024-8952","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":6.8,"headline":"SSRF in composiohq/composio","id":"CVE-2024-8955","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":6.4,"headline":"Composio Command Execution vulnerability","id":"CVE-2024-53526","kev_date_added":null,"published":"2025-01-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"total"},"state":"PUBLISHED","updated":"2025-03-20","vendors":["composiohq"]},"summary":"Attackers can execute arbitrary code via the mathematical_calculator endpoint due to unsafe eval usage in the composio library.","url":"https://insights.sbomify.com/CVE-2024-8953/"}