{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5151 exists.","fix":"No fix has been published for CVE-2025-5151 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-5151 is a medium-severity code injection vulnerability in defog-ai introspect, published on 25 May 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-5151 and fix it if it is affected.\n\nWhat it is: CVE-2025-5151 is a medium-severity code injection vulnerability in defog-ai introspect, published on 25 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5151 exists.\n\nAffected product: defog-ai introspect. 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-5151/ (Markdown: https://insights.sbomify.com/CVE-2025-5151/index.md)","id":"CVE-2025-5151","markdown":"https://insights.sbomify.com/CVE-2025-5151/index.md","name":"CVE-2025-5151","record":{"aliases":["GHSA-cvw4-vc58-fhx4"],"analysis":{"component_type":"library","fix_type":"workaround","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"defog-ai introspect library","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary code via the execute_analysis_code_safely function in defog-ai introspect, requiring local access or specific environment assumptions.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"introspect","vendor":"defog"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"A vulnerability classified as critical has been found in defog-ai introspect up to 0.1.4. This affects the function execute_analysis_code_safely of the file introspect/backend/tools/analysis_tools.py. The manipulation of the argument code leads to code injection. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used. The patch is named 502. It is recommended to apply a patch to fix this issue. The code maintainer explains, that \"[they] have added some workarounds to address this in #502, but will not be implementing a full fix. This is because this repo is meant to be run in a docker environment, which will significantly mitigate potential security risks. Having said that, we have added a SECURITY section in our README to make this clearer to users.\"","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":"defog-ai introspect analysis_tools.py execute_analysis_code_safely code injection","id":"CVE-2025-5151","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"Chanjet CRM newActivityedit.php sql injection","id":"CVE-2025-5152"},"packages":[],"prev":{"headline":"docarray Web API torch_dataset.py __getitem__ prototype pollution","id":"CVE-2025-5150"},"products":["introspect"],"published":"2025-05-25","related":[],"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-05-28","vendors":["defog-ai"]},"summary":"Attackers can execute arbitrary code via the execute_analysis_code_safely function in defog-ai introspect, requiring local access or specific environment assumptions.","url":"https://insights.sbomify.com/CVE-2025-5151/"}