Quick answers
- Is CVE-2026-16195 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-16195 being exploited in the wild.
- How severe is CVE-2026-16195?
- Medium severity, with a CVSS score of 6.3, published 18 July 2026.
- Which products and versions are affected?
- Sipeed PicoClaw <= 0.2.9.
- Is there a fix for CVE-2026-16195?
- 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-16195 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-16195?
- 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
An incorrect authorization vulnerability exists in the `dispatchIncoming` function within `pkg/channels/wecom/wecom.go` of Sipeed PicoClaw. The WeCom inbound channel fails to invoke the `ShouldRespondInGroup` validation helper, which is responsible for enforcing the `mention_only` policy. Consequently, even if `channels.wecom.group_trigger.mention_only` is set to true, the application forwards all group messages to the internal inbound bus. A remote attacker with basic group participant privileges can exploit this to trigger agent execution and downstream tool invocations without the required bot mention. As of the advisory date, no patched version is available.
Affected products
- Sipeed PicoClaw <= 0.2.9
Timeline
- 2026-07-18: disclosed: Vulnerability disclosed via GitHub issue and NVD