VulnerabilityPublished 15 Mar 2026

CVE-2026-4198: hypermodel-labs mcp-server-auto-commit · Command Injection

Affects hypermodel-labs mcp-server-auto-commitSource CVE Database V5

Compare

Public exploit available · CVSS 4.8 Medium.

Data as of 29 Oct 2026, 19:04 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 15 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 29 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
hypermodel-labsmcp-server-auto-commit	Affected =1.0.0	Fixed in–
GitHubhypermodel-labs/mcp-server-auto-commit`pkg:github/hypermodel-labs/mcp-server-auto-commit`Other threats	Affected =1.0.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-4198, organizations should immediately apply the official patch identified by commit f7d992c830c5f2ec5749852e66c0195e3ed7fe30 to upgrade mcp-server-auto-commit beyond version 1.0.0. Until patched, restrict local access to systems running this software to trusted users only and monitor for suspicious command execution activities. Implement strict access controls and auditing on developer and CI/CD environments where this tool is deployed. Consider isolating build and commit automation servers from general user environments to reduce the risk of local exploitation. Additionally, review and sanitize any inputs passed to the getGitChanges function or similar command execution contexts in custom forks or integrations. Employ endpoint detection and response (EDR) solutions to detect anomalous command executions indicative of exploitation attempts. Finally, maintain an inventory of affected software versions and ensure timely updates as part of vulnerability management processes.

Description

CVE-2026-4198 is a command injection vulnerability in hypermodel-labs mcp-server-auto-commit version 1.0.0, specifically in the getGitChanges function of index.ts. The flaw allows an attacker with local access and low privileges to execute arbitrary commands on the host system. Exploitation does not require user interaction but is limited to local attack vectors. Although the vulnerability has a medium CVSS score of 4.8, it poses a risk to confidentiality, integrity, and availability due to potential command execution. The vendor has been notified but has not yet responded, and a patch is available to remediate the issue. No known exploits are currently in the wild.

Impact

The primary impact of CVE-2026-4198 is the potential for local attackers to execute arbitrary commands on systems running the vulnerable mcp-server-auto-commit 1.0.0 software. This could lead to unauthorized access to sensitive data, modification or deletion of files, and disruption of service availability. Since the vulnerability requires local access, the risk is higher in environments where multiple users have access to the same system or where attackers can gain initial foothold through other means (e.g., compromised credentials or insider threats). Organizations relying on this software for automated commit or deployment processes may face risks of supply chain compromise or unauthorized code changes. The medium severity rating reflects the limited attack vector but significant consequences if exploited. Failure to patch could allow attackers to escalate privileges or move laterally within a network, especially in development or CI/CD environments where this tool is used.

References

Community reviews

Loading reviews…