A security vulnerability has been detected in Sipeed PicoClaw up to 0.2.9. This affects the function IPAllowlist of the file web/backend/middleware/access_control.go of the component Launcher. Such manipulation leads to improper access controls. The attack may be performed from remote. The exploit has been disclosed publicly and may be used. The name of the patch is 3126. A patch should be applied to remediate this issue.
CVE-2026-15319
Score 7.3 from GitHub Security Advisory published 2026-07-10. a secondary CVSS source baseline 7.3; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.3
- EG Score
- 7.3(high)
- EPSS
- 24.3%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 10, 2026
Advisory Details (3)
Auto-updated Jul 10, 2026fix(web): improve launcher allowlist bypass diagnostics
Fix merged in sipeed/picoclaw PR #3126 on 2026-06-15 — awaiting tagged release
https://github.com/sipeed/picoclaw/pull/3126[Security] PicoClaw launcher `allowed_cidrs` can be bypassed through a same-host reverse proxy because access control trusts `RemoteAddr` · Issue #3069 · sipeed/picoclaw · GitHub
https://github.com/sipeed/picoclaw/issues/3069GitHub - sipeed/picoclaw: Tiny, Fast, and Deployable anywhere — automate the mundane, unleash your creativity · GitHub
https://github.com/sipeed/picoclaw/Vendor Advisories for CVE-2026-15319(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 17× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-12 08:48 UTCEG score recompute
- 2026-07-12 08:48 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 21:57 UTCEG score recompute
- 2026-07-11 21:57 UTCGHSA enrichment
- 2026-07-11 11:07 UTCEG score recompute
- 2026-07-11 11:06 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 00:16 UTCEG score recompute
- 2026-07-11 00:15 UTCGHSA enrichment
- 2026-07-10 16:18 UTCNVD updateCVSS v4 → 5.5
- 2026-07-10 14:42 UTCMITRE cvelistV5CVSS v4 → 6.9
- 2026-07-10 13:25 UTCEG score recompute
- 2026-07-10 13:25 UTCGHSA enrichment
- 2026-07-10 04:54 UTCNVD updateCVSS v4 → 5.5
- 2026-07-10 02:33 UTCEG score recompute
- 2026-07-10 02:30 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-284
- CVE-2015-10057NVD 4.6EG 9.8MEDIUM
- CVE-2010-5305EG 9.8EPSS 92%CRITICAL
- CVE-2015-9209EG 9.8CRITICAL
- CVE-2015-9152EG 9.8CRITICAL
- CVE-2014-10059EG 9.8CRITICAL
- CVE-2014-10053EG 9.8CRITICAL
- CVE-2014-10050EG 9.8CRITICAL
- CVE-2015-0150EG 9.8CRITICAL
- CVE-2014-2048EG 9.8CRITICAL
- CVE-2013-0422EG 9.8 KEVEPSS 100%CRITICAL
Frequently asked(5)
What is CVE-2026-15319?
When was CVE-2026-15319 disclosed?
Is CVE-2026-15319 actively exploited?
What is the CVSS score of CVE-2026-15319?
How do I remediate CVE-2026-15319?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15319
Is Your Infrastructure Affected by CVE-2026-15319?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.