Quick answers
- Is CVE-2026-15320 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-15320 being exploited in the wild.
- How severe is CVE-2026-15320?
- Medium severity, with a CVSS score of 5.4, published 10 July 2026.
- Which products and versions are affected?
- Sipeed PicoClaw up to 0.2.9.
- Is there a fix for CVE-2026-15320?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-15320 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-15320?
- Check whether you run Sipeed PicoClaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A missing authorization check in the PicoClaw command execution pipeline allows users authenticated to the Pico WebSocket channel to invoke administrative actions. Specifically, the `rt.ReloadConfig` function in `pkg/channels/pico/pico.go` can be triggered by sending a `/reload` command within a standard `message.send` payload. While the dedicated HTTP management endpoint `/reload` correctly enforces bearer-token authorization, the chat-based command path fails to verify if the sender has administrative privileges. An attacker with a valid Pico chat token can remotely force a configuration reload, leading to a service restart and potential availability issues. The vulnerability is present in versions up to 0.2.9.
Affected products
- Sipeed PicoClaw up to 0.2.9
Timeline
- 2026-07-10: advisory: NVD publication date
- 2026-07-10: disclosed: Public exploit availability reported