{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4199 exists.","fix":"No fix has been published for CVE-2026-4199 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-4199 is a medium-severity command injection vulnerability in bazinga012 mcp_code_executor, published on 16 Mar 2026. 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-2026-4199 and fix it if it is affected.\n\nWhat it is: CVE-2026-4199 is a medium-severity command injection vulnerability in bazinga012 mcp_code_executor, published on 16 Mar 2026. 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-2026-4199 exists.\n\nAffected product: bazinga012 mcp_code_executor. 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-4199/ (Markdown: https://insights.sbomify.com/CVE-2026-4199/index.md)","id":"CVE-2026-4199","markdown":"https://insights.sbomify.com/CVE-2026-4199/index.md","name":"CVE-2026-4199","record":{"aliases":["GHSA-wf6m-m2x3-f49p"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"MCP code executor","requires_auth":"low_privilege","summary":"Local attackers can execute arbitrary commands via the installDependencies function in the mcp_code_executor library.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"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/E:P","version":"4.0"},"cwes":[{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"},{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"A vulnerability was identified in bazinga012 mcp_code_executor up to 0.3.0. Affected by this issue is the function installDependencies of the file src/index.ts. Such manipulation leads to command injection. The attack can only be performed from a local environment. The exploit is publicly available and might be used. It is best practice to apply a patch to resolve this issue. The project was informed of the problem early through an issue report but has not responded yet.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"bazinga012 mcp_code_executor index.ts installDependencies command injection","id":"CVE-2026-4199","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"glowxq glowxq-oj ProblemCaseController.java uploadTestcaseZipUrl server-side request forgery","id":"CVE-2026-4200"},"packages":[],"prev":{"headline":"hypermodel-labs mcp-server-auto-commit index.ts getGitChanges command injection","id":"CVE-2026-4198"},"products":["mcp_code_executor"],"published":"2026-03-16","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)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-16","vendors":["bazinga012"]},"summary":"Local attackers can execute arbitrary commands via the installDependencies function in the mcp_code_executor library.","url":"https://insights.sbomify.com/CVE-2026-4199/"}