ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-4199

A vulnerability was identified in bazinga012 mcp_code_executor up to 0.3.0.

Published Mar 16, 2026 · catalog updated Jun 17, 2026 · A vulnerability was identified

Check if you run it

No confirmed exploitation is on record for CVE-2026-4199. EPSS is 1.13%. Act only if a listed version of A vulnerability was identified is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (A vulnerability was identified).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Low1.9
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
1.13%
Remediation
Advisory link
Affected products
See sources for product scope

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.

No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.

How to fix CVE-2026-4199

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-4199. EPSS is 1.13%. Act only if a listed version of A vulnerability was identified is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-74: Injection; CWE-77: Command Injection. EPSS 1.13%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 16, 2026 · NIST NVD

    Detected

    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 infor

  2. Jun 17, 2026 · NIST NVD

    Updated

    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 infor

Sources

  • CVE.orgVulnerability recordCVE-2026-4199

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-4199

    30-day exploitation probability 1.1%

    first.org
  • NIST NVDVulnerability recordCVE-2026-4199

    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

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.