Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege application credentials
-
DeliverySend crafted request to Default Local Worker Backend
-
ExploitInject OS command metacharacters into unsanitized input
-
ExecutionBackend passes payload to system shell
-
ImpactExecute arbitrary OS commands as Muteki process user
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK
2 techniques across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires low-level privileges (PR:L per CVSS 4.0 vector) - the attacker must have some authenticated or credentialed access to the Muteki application, or the ability to influence the contents of the .claude/settings.json configuration file processed by the Default Local Worker Backend. The attack is network-reachable (AV:N) with low complexity (AC:L) and no required user interaction (UI:N), meaning once authentication is satisfied the exploit can be executed remotely without further prerequisites. No special non-default configuration is indicated as required beyond running the Muteki software itself. Limiting factors: requires at minimum low-privilege access to the application; the product's small and declining user base limits the attack surface globally; and the obscurity of the application reduces adversarial targeting interest compared to mainstream software. |
| Impact | The CVSS 4.0 score of 5.3 with low VC/VI/VA impacts is notably lower than what CWE-78 OS command injection typically warrants - a discrepancy that should prompt verification. Independent assessment suggests the actual integrity and confidentiality impacts could be higher if command execution is unrestricted on the server; the vendor's low impact scoring may reflect application-level sandboxing or a highly constrained execution environment, but this is not confirmed from available data. The E:P exploit maturity flag in the CVSS 4.0 vector confirms a public POC exists, which materially raises real-world exploitability. However, the product is obscure (single GitHub repository, small open-source project) and the maintainer has announced a shutdown, meaning the installed base is minimal. No EPSS data is available in the provided intelligence. KEV status is absent, so no confirmed active exploitation is on record. The realistic risk is narrow: low prevalence product with a public POC and no patch path - dangerous for the small number of deployments that exist, but not a broad enterprise threat. |
| Exploit ScenarioDerived | An attacker with low-privilege access to the Muteki application - such as an authenticated API user or a user with write access to the application's configuration path - crafts a payload embedding OS command metacharacters into an input field or configuration value processed by the Default Local Worker Backend. The application passes this unsanitized input to a system shell call, executing the injected commands with the privileges of the Muteki process. A public POC exists at https://github.com/micr0softDrestlife/muteki_vul_report, lowering the barrier to exploitation significantly. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 25, 2026
OS command injection in FishCodeTech Muteki up to version 0.2.5 enables remote low-privileged attackers to execute arbitrary operating system commands through unsanitized input handled by the Default Local Worker Backend component, specifically via the application's .claude/settings.json configuration file. Publicly available exploit code (POC) exists, referenced from a dedicated exploit report repository, raising the practical exploitability despite the product's limited deployment footprint. The project maintainer closed the issue without a patch, announcing that Muteki will be refactored and shut down, making this effectively an unpatched, end-of-life vulnerability with no vendor remediation path. No public exploit identified at time of analysis as confirmed active exploitation by CISA KEV.
RemediationAI
No vendor-released patch is available and none is expected - the project maintainer closed the vulnerability issue with a statement (translated from Chinese) that the project will be refactored and shut down. The primary remediation for any active deployment of Muteki up to 0.2.5 is immediate decommissioning of the software. If decommissioning is not immediately possible, restrict network access to the Default Local Worker Backend endpoint to trusted hosts only via firewall or network segmentation, preventing remote exploitation. Additionally, remove or restrict write access to the .claude/settings.json configuration file to prevent injection via that vector. Treat any instance as compromised until isolated. Reference: https://vuldb.com/vuln/394962 and exploit details at https://github.com/micr0softDrestlife/muteki_vul_report.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-78 (Improper Neutralization of Special Elements used in an OS Command) describes failures to sanitize user-controlled input before passing it to a system shell. In Muteki's Default Local Worker Backend, input processed via or alongside the .claude/settings.json configuration file is apparently passed directly or insufficiently sanitized into an OS-level command execution context. The affected CPE is cpe:2.3:a:fishcodetech:muteki:*:*:*:*:*:*:*:* covering all known versions up to and including 0.2.5. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) indicates the attack is network-reachable with low complexity and requires low-level privileges - consistent with an authenticated but low-barrier API or backend endpoint that fails to properly separate data from command context. The E:P exploit maturity tag in the CVSS 4.0 vector corroborates the publicly disclosed POC repository.
Know when Muteki gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Network-reachable with low privileges required; scope unchanged; impacts set to Low matching vendor's 4.0 scoring, though CWE-78 typically warrants higher - sandboxing context unconfirmed.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
3DescriptionCVE.org
A security vulnerability has been detected in FishCodeTech Muteki up to 0.2.5. The affected element is an unknown function of the file .claude/settings.json of the component Default Local Worker Backend. The manipulation leads to os command injection. The attack can be initiated remotely. The exploit has been disclosed publicly and may be used. The issue was closed with the comment (translated from Chinese): "The project will be refactored and shut down."
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
EUVD-2026-65491
GHSA-w4x2-2pcx-2cpc
NVD
CVE.org
EPSS
VulDB
Exploit-DB