CVE-2026-15320: Sipeed PicoClaw Authorization Bypass Vulnerability

Technical summary

CVE-2026-15320 is a missing authorization vulnerability in the rt.ReloadConfig function within pkg/channels/pico/pico.go of Sipeed PicoClaw. The flaw stems from insufficient authorization validation when processing the message.send argument during configuration reload operations. An attacker with valid credentials can craft a malicious message to bypass authorization controls, leading to integrity compromise and potential availability impact. The vulnerability is categorized under CWE-862 (Missing Authorization) and CWE-863 (Incorrect Authorization), indicating that the application fails to verify user permissions before allowing sensitive operations.

Business impact

An authenticated attacker exploiting this vulnerability could alter system configuration or trigger denial-of-service conditions, potentially disrupting PicoClaw deployments in production environments. The impact is moderate but meaningful: system administrators may experience unexpected configuration changes, service interruptions, or require emergency recovery procedures. Organizations relying on PicoClaw for critical workflows should consider this a moderate business risk, particularly if deployed in multi-tenant or shared environments where user isolation is important.

Affected systems

Sipeed PicoClaw version 0.2.9 and all earlier versions are confirmed affected. Verify your installed version by checking the release information or running the application's version command. Organizations should conduct an inventory of PicoClaw deployments across their infrastructure to determine exposure scope.

Exploitability

This vulnerability has low barriers to exploitation. An attacker must possess valid credentials to the PicoClaw system (PR:L in the CVSS vector), but no special elevated privileges are required. The attack is network-accessible and does not require user interaction. Public exploit code is now available, reducing the technical skill required for weaponization. The combination of network accessibility, low privilege requirements, and publicly available proof-of-concept increases the practical exploitability risk.

Remediation

Update Sipeed PicoClaw to a version newer than 0.2.9 as soon as a patch is released. Until a fix is available, restrict network access to PicoClaw instances using firewall rules, and limit user account provisioning to trusted personnel only. Review authentication logs for suspicious configuration reload patterns. Consider running PicoClaw in isolated network segments or behind VPN access controls to reduce attack surface.

Patch guidance

Monitor Sipeed's official repository and release channels for a patched version addressing this authorization bypass. Verify the fix includes proper authorization validation in the rt.ReloadConfig function before accepting a patch. Test any update in a non-production environment first to ensure compatibility with your deployment. No specific patch version is documented in current advisories; consult the vendor's security announcements for the recommended update path.

Detection guidance

Search logs for rt.ReloadConfig invocations with unusual or mismatched authorization contexts. Monitor for configuration reload requests originating from non-administrative accounts or unexpected source IPs. Implement alerting on failed authorization attempts followed by successful configuration modifications. If PicoClaw emits structured logs, filter for message.send argument manipulations in the pico channel handler. Network detection could flag unusual configuration management traffic if baseline behavior is established.

Why prioritize this

Although the CVSS score is moderate (5.4), prioritize this vulnerability because public exploit code is available, lowering the barrier to opportunistic attacks. The flaw allows authenticated users to escalate their capabilities beyond their intended authorization level, which is a common attack pattern in multi-user systems. Organizations with internet-facing or multi-tenant PicoClaw deployments should treat this as higher priority than the base score alone suggests.

Risk score, explained

The CVSS 3.1 score of 5.4 (MEDIUM) reflects the requirement for valid authentication (PR:L) and the local scope of impact. However, the score does not fully capture the risk posed by publicly available exploit code or the likelihood of privilege escalation attempts in shared environments. The integrity and availability impacts are marked as low (I:L, A:L) because the damage per exploitation is incremental, not catastrophic—but cumulative or repeated exploitation could compound harm.

Frequently asked questions