# CVE-2026-16197: Sipeed PicoClaw Group Message feishu_64.go handleMessageReceive authorization

> Attackers can bypass authorization in the group message handler to perform unauthorized actions remotely.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-3c84-2qg9-24p8

## What is CVE-2026-16197?

CVE-2026-16197 is a medium-severity missing authorization vulnerability in Sipeed PicoClaw, published on 18 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in Sipeed PicoClaw up to 0.2.9. The affected element is the function handleMessageReceive of the file pkg/channels/feishu/feishu_64.go of the component Group Message Handler. Such manipulation leads to missing authorization. The attack can be launched remotely. The exploit has been disclosed publicly and may be used. The reported GitHub issue was closed automatically due to inactivity.

Weakness: CWE-863 (Incorrect Authorization), CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-16197 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16197 is a medium-severity missing authorization vulnerability in Sipeed PicoClaw, published on 18 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16197 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-16197/ (Markdown: https://insights.sbomify.com/CVE-2026-16197/index.md)
```

## Sources

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

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