CVE-2026-6987

7.3

Sipeed · PicoClaw

A command injection vulnerability exists in the Web Launcher Management Plane component of PicoClaw via the /api/gateway/restart endpoint, allowing for unauthenticated remote code execution.

Executive summary

PicoClaw versions 0.2.4 and earlier are vulnerable to a remote command injection flaw that allows unauthenticated attackers to execute arbitrary system commands.

Vulnerability

The application is susceptible to command injection (CWE-77) within the /api/gateway/restart function of the Web Launcher Management Plane, which does not properly sanitize user-supplied input. The vulnerability is remotely exploitable by an unauthenticated attacker.

Business impact

Successful exploitation allows an attacker to execute arbitrary commands on the host operating system, potentially leading to full system compromise. With a CVSS score of 7.3, this high-severity flaw poses a significant risk to data confidentiality and system integrity. Unauthorized access to the management plane could facilitate further lateral movement within the network or the deployment of malicious payloads.

Remediation

Immediate Action: As no official patch is currently available, administrators should restrict network access to the Web Launcher Management Plane and disable the affected service if it is not business-critical.

Proactive Monitoring: Monitor server logs and system process activity for unexpected execution of shell commands or suspicious network connections originating from the PicoClaw instance.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block malicious payloads targeting the /api/gateway/restart endpoint.

Exploitation status

Public Exploit Available: Unknown.

Analyst recommendation

Given the severity of a command injection vulnerability and the current lack of a vendor patch, organizations should prioritize isolating the affected PicoClaw instances from untrusted network segments. Continuous monitoring for indicators of compromise is essential until a secure version is released by the project maintainers.

More Sipeed CVEs

Sources

Originally found and disclosed by AiSec (VulDB User), with VulDB CNA Team (coordinator), per the CVE Program record.