Quick answers
- Is CVE-2026-16197 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-16197 being exploited in the wild.
- How severe is CVE-2026-16197?
- 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-16197?
- 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-16197 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-16197?
- 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 exists in the Feishu channel's message handling logic within `pkg/channels/feishu/feishu_64.go`. While the `handleMessageReceive` function validates the current sender against the `allow_from` list, the `prependReplyContext` function fetches and imports the body of parent/replied messages without re-verifying the original author's authorization status. A remote attacker who is not on the allowlist can exploit this by having an authorized user reply to their message, causing the untrusted content to be injected into the downstream AI agent's context. This can be used for prompt injection or to influence automated decisions. As of the advisory date, no official patch has been confirmed.
Affected products
- Sipeed PicoClaw <= 0.2.9
Timeline
- 2026-07-18: disclosed: Vulnerability disclosed via GitHub issue and NVD