VulnerabilityPublished 11 Mar 2026

CVE-2026-3959: 0xKoda WireMCP · OS Command Injection

Affects 0xKoda WireMCPSource CVE Database V5

Compare

Public exploit available · CVSS 4.8 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

4.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Base metrics

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
0xKodaWireMCP	Affected =7f45f8b2b4adeb76be8c6227eefb38533fdd6b1e	Fixed in–

AI-suggested

To mitigate this vulnerability, organizations should first restrict local access to systems running WireMCP to trusted personnel only, minimizing the risk of local exploitation. Employ strict access controls and monitoring to detect unauthorized local activity. Until a vendor patch or update is available, consider isolating WireMCP instances in hardened environments or containers to limit the impact of potential command injection. Review and audit the usage of the Tshark CLI Command Handler component and avoid exposing it unnecessarily. If possible, apply custom input validation or sanitization at the application or system level to prevent injection of malicious commands. Monitor system logs for suspicious command execution patterns. Engage with the 0xKoda project or community to track any forthcoming patches or mitigations. Additionally, implement endpoint detection and response (EDR) solutions to detect anomalous command executions indicative of exploitation attempts. Finally, maintain regular backups and incident response plans to recover quickly if exploitation occurs.

Description

CVE-2026-3959 is an OS command injection vulnerability in the 0xKoda WireMCP product, specifically in the Tshark CLI Command Handler's server.tool function within index.js. The flaw allows an attacker with local access and low privileges to execute arbitrary OS commands by manipulating inputs to this function. Exploitation does not require user interaction but does require local access and low complexity. The vulnerability has a medium severity with a CVSS score of 4.8. No patch or vendor response has been provided yet, and the product uses a rolling release system complicating version tracking. While no known exploits are currently in the wild, the exploit details have been publicly disclosed. Organizations using WireMCP should be cautious of local threat actors leveraging this vulnerability to escalate privileges or execute malicious commands.

Impact

The impact of this vulnerability is primarily on confidentiality, integrity, and availability of systems running 0xKoda WireMCP. Since the flaw allows OS command injection, an attacker with local access could execute arbitrary commands, potentially leading to unauthorized data access, modification, or deletion. This could also enable privilege escalation if the WireMCP process runs with elevated permissions. Availability could be affected if malicious commands disrupt service or crash the application. Organizations relying on WireMCP for network monitoring or management could face operational disruptions or data breaches. The requirement for local access limits remote exploitation but insider threats or attackers who have gained initial footholds could leverage this vulnerability to deepen their control. The lack of vendor response and patch availability increases the risk exposure period. Overall, the vulnerability poses a moderate risk but could be critical in environments where WireMCP is deployed on sensitive or critical infrastructure with multiple local users.

References

Community reviews

Loading reviews…