CVE-2026-2178VulnerabilityPublished 8 Feb 2026Updated 23 Feb 2026

CVE-2026-2178: r-huijts xcode-mcp-server · Command Injection

Affects r-huijts xcode-mcp-serverSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.3Medium

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

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

CVSS:4.0/AV:N/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: Network
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: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
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 8 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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
r-huijtsxcode-mcp-server	Affected =f3419f00117aa9949e326f78cc940166c88f18cb	Fixed in–

AI-suggested

To mitigate CVE-2026-2178, organizations should immediately apply the patch identified by commit 11f8d6bacadd153beee649f92a78a9dad761f56f to their xcode-mcp-server installations. Given the rolling release model, ensure that the deployment pipeline incorporates this fix promptly. Additionally, implement strict input validation and sanitization on all parameters, especially those that influence command execution, to prevent injection attacks. Restrict network access to the xcode-mcp-server to trusted internal networks or VPNs to reduce exposure. Employ runtime application self-protection (RASP) or intrusion detection systems to monitor for anomalous command execution patterns. Regularly audit logs for suspicious activity related to the registerXcodeTools function. Finally, consider isolating the server in a hardened environment with minimal privileges to limit the potential impact of any successful exploitation.

Description

A vulnerability was found in r-huijts xcode-mcp-server up to f3419f00117aa9949e326f78cc940166c88f18cb. This affects the function registerXcodeTools of the file src/tools/xcode/index.ts of the component run_lldb. The manipulation of the argument args results in command injection. It is possible to launch the attack remotely. The exploit has been made public and could be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available. The patch is identified as 11f8d6bacadd153beee649f92a78a9dad761f56f. Applying a patch is advised to resolve this issue.

Impact

The impact of CVE-2026-2178 on organizations is significant due to the ability of remote attackers to execute arbitrary commands on affected xcode-mcp-server instances without authentication. This can lead to unauthorized access to sensitive data (confidentiality impact), modification or corruption of data or system configurations (integrity impact), and potential denial of service or disruption of development workflows (availability impact). Since the xcode-mcp-server is likely used in software development environments, exploitation could compromise build processes, inject malicious code into software artifacts, or disrupt continuous integration pipelines. The medium CVSS score reflects that while the attack is straightforward, the scope of impact is somewhat limited to the affected server and its environment. However, in organizations heavily reliant on this tool, the consequences could cascade into broader operational and security risks. The public availability of exploit code increases the urgency for mitigation to prevent opportunistic attacks.

Summary

CVE-2026-2178 is a command injection vulnerability found in the r-huijts xcode-mcp-server, a component involved in managing Xcode tools, specifically within the registerXcodeTools function located in src/tools/xcode/index.ts under the run_lldb component. The vulnerability is caused by improper sanitization or validation of the args argument, which an attacker can manipulate to inject and execute arbitrary system commands remotely. This flaw does not require authentication or user interaction, making it easier to exploit over the network. The product follows a rolling release model, complicating precise version identification, but the vulnerability affects all versions up to commit f3419f00117aa9949e326f78cc940166c88f18cb. A patch has been committed (11f8d6bacadd153beee649f92a78a9dad761f56f) to fix the issue. The CVSS 4.0 base score is 5.3, reflecting medium severity due to network attack vector, low complexity, no privileges required, and no user interaction needed, but limited impact scope and partial confidentiality, integrity, and availability impacts. Although no active exploits have been reported in the wild, the public disclosure of the exploit code increases the likelihood of exploitation attempts. The vulnerability could allow attackers to execute arbitrary commands on the server, potentially leading to unauthorized data access, modification, or service disruption.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 21:42 UTC

Technical details

References

Community reviews

Related threats