CVE-2026-15319: Sipeed PicoClaw Auth Bypass Vulnerability

CVE-2026-15319 Overview

CVE-2026-15319 is an improper access control vulnerability affecting Sipeed PicoClaw versions up to 0.2.9. The flaw resides in the IPAllowlist function within web/backend/middleware/access_control.go, part of the Launcher component. Remote attackers can manipulate the allowlist logic to bypass access restrictions without requiring authentication or user interaction. The exploit has been disclosed publicly, increasing the likelihood of opportunistic attacks. Sipeed released patch 3126 to remediate the issue. This vulnerability is classified under [CWE-266: Incorrect Privilege Assignment].

Critical Impact
Remote attackers can bypass IP-based access controls in the PicoClaw Launcher, potentially reaching backend functionality intended to be restricted.

Affected Products

Sipeed PicoClaw versions up to and including 0.2.9
Launcher component containing web/backend/middleware/access_control.go
Deployments exposing the PicoClaw web backend to untrusted networks

Discovery Timeline

2026-07-10 - CVE-2026-15319 published to NVD
2026-07-10 - Last updated in NVD database

Technical Details for CVE-2026-15319

Vulnerability Analysis

The vulnerability exists in the IPAllowlist middleware function of the PicoClaw Launcher. This middleware is responsible for restricting backend access to approved source IP addresses. Improper implementation of the allowlist logic allows remote requests to bypass the intended access control checks. Because the middleware operates on the network-facing web backend, exploitation requires only network reachability to the Launcher service.

Successful exploitation grants an attacker access to backend routes that should be gated by IP restrictions. The impact spans limited confidentiality, integrity, and availability effects on the affected system, as reflected in the vulnerability's scoring.

Root Cause

The root cause is flawed access control logic in web/backend/middleware/access_control.go. The IPAllowlist function does not correctly validate the client source address before permitting request flow to protected handlers. Common patterns behind this class of issue include trusting client-supplied headers such as X-Forwarded-For, incorrect CIDR matching, or default-allow behavior when the allowlist is empty or misparsed. The upstream patch 3126 corrects the middleware behavior.

Attack Vector

The attack vector is network-based and requires no authentication or user interaction. An attacker sends crafted HTTP requests directly to the PicoClaw Launcher backend from a non-allowlisted source. Because the exploit is publicly disclosed, opportunistic scanning for exposed PicoClaw instances is a realistic threat model.

No verified proof-of-concept code has been published in the referenced advisories. See the GitHub Issue #3069 on PicoClaw and GitHub Pull Request #3126 for PicoClaw for technical remediation details.

Detection Methods for CVE-2026-15319

Indicators of Compromise

HTTP requests to PicoClaw Launcher backend endpoints originating from source IPs outside the configured allowlist.
Requests containing spoofed proxy headers such as X-Forwarded-For or X-Real-IP targeting /web/backend/ routes.
Access log entries showing successful 2xx responses to sensitive Launcher routes from unexpected geolocations.

Detection Strategies

Compare web access logs against the configured IPAllowlist to identify requests that were served despite falling outside allowed ranges.
Alert on any inbound traffic to PicoClaw Launcher ports from public networks when the deployment is intended to be internal-only.
Instrument the access_control.go middleware with structured logging to record allow/deny decisions and the client IP used for evaluation.

Monitoring Recommendations

Ingest PicoClaw Launcher access logs into a centralized SIEM or data lake for correlation with network telemetry.
Monitor for repeated probing of Launcher endpoints, which may indicate exploitation attempts against exposed instances.
Track version inventory across deployments to identify hosts still running PicoClaw 0.2.9 or earlier.

How to Mitigate CVE-2026-15319

Immediate Actions Required

Apply the upstream fix from GitHub Pull Request #3126 for PicoClaw to all affected PicoClaw installations.
Restrict network exposure of the PicoClaw Launcher backend using firewall rules or a reverse proxy that enforces IP restrictions independently of the application layer.
Audit existing access logs for requests that reached protected endpoints from unexpected source IPs.

Patch Information

Sipeed has published patch 3126 in the PicoClaw repository. Users should update to a version that includes this commit and verify that the IPAllowlist middleware in web/backend/middleware/access_control.go reflects the fix. Refer to the GitHub Repository for PicoClaw and VulDB CVE-2026-15319 Overview for reference.

Workarounds

Place the PicoClaw Launcher behind a hardened reverse proxy or firewall that enforces source-IP restrictions before requests reach the application middleware.
Disable or block external access to the Launcher backend until the patch is applied.
Configure network segmentation so the Launcher is only reachable from trusted management networks.

bash

# Example: restrict PicoClaw Launcher exposure with iptables
# Allow only the trusted management subnet to reach the backend port
iptables -A INPUT -p tcp --dport 8080 -s 10.0.0.0/24 -j ACCEPT
iptables -A INPUT -p tcp --dport 8080 -j DROP