Unauthenticated route access via loopback proxy trust
Published Jul 10, 2026 · Updated Jul 10, 2026
Access control bypass in Sipeed PicoClaw’s unreleased launcher allows remote attackers to reach restricted routes through a same-host proxy. The IPAllowlist middleware derives client identity only from RemoteAddr and unconditionally accepts loopback peers, so a local proxy makes external requests appear local. The upstream report states that no published release tag contains the affected middleware, contradicting the CNA’s 0.2.0 through 0.2.9 range; exposure requires public mode, allowed_cidrs, and a same-host reverse proxy or tunnel.
Summary
What happened
Access control bypass in Sipeed PicoClaw’s unreleased launcher allows remote attackers to reach restricted routes through a same-host proxy. The IPAllowlist middleware derives client identity only from RemoteAddr and unconditionally accepts loopback peers, so a local proxy makes external requests appear local. The upstream report states that no published release tag contains the affected middleware, contradicting the CNA’s 0.2.0 through 0.2.9 range; exposure requires public mode, allowed_cidrs, and a same-host reverse proxy or tunnel.
The record
- CVE
- CVE-2026-15319
- Published
- Jul 10, 2026
- Updated
- Jul 10, 2026
- Vendor
- Sipeed
- Product
- PicoClaw
- Classifications
- CWE-266, CWE-284, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 10, 2026CVE publishedPublication date reported by the CVE source.
- Jul 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.2.0
- Affected versionversion=0.2.1
- Affected versionversion=0.2.2
- Affected versionversion=0.2.3
- Affected versionversion=0.2.4
- Affected versionversion=0.2.5
- Affected versionversion=0.2.6
- Affected versionversion=0.2.7
- Affected versionversion=0.2.8
- Affected versionversion=0.2.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- verification_test.py loopback-proxy proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo