# CVE-2026-15319: Sipeed PicoClaw Launcher access_control.go IPAllowlist access control

> Remote attackers can bypass IP allowlist restrictions in the PicoClaw Launcher due to improper access control implementation.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-f9rq-5867-x4mq

## What is CVE-2026-15319?

CVE-2026-15319 is a medium-severity missing authorization vulnerability in Sipeed PicoClaw, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-284 (Improper Access Control), CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2026-15319?


## How do I fix CVE-2026-15319?

No fix has been published for CVE-2026-15319 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-15319 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15319 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15319 and fix it if it is affected.

What it is: CVE-2026-15319 is a medium-severity missing authorization vulnerability in Sipeed PicoClaw, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15319 exists.

Affected product: Sipeed PicoClaw. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-15319/ (Markdown: https://insights.sbomify.com/CVE-2026-15319/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-15319
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-15319
- OSV: https://osv.dev/vulnerability/CVE-2026-15319

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-15319/
Summaries are generated and may contain mistakes; the official description above is the record.