# CVE-2026-16196: Sipeed PicoClaw web_fetch web.go isPrivateOrRestrictedIP server-side request forgery

> Remote attackers can exploit a flaw in PicoClaw's web_fetch to perform server-side request forgery, potentially accessing internal resources.

- **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:** 22 Jul 2026
- **Also known as:** GHSA-vf62-q3j8-cj9g

## What is CVE-2026-16196?

CVE-2026-16196 is a medium-severity server-side request forgery 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 weakness has been identified in Sipeed PicoClaw up to 0.2.9. Impacted is the function isPrivateOrRestrictedIP of the file pkg/tools/integration/web.go of the component web_fetch. This manipulation causes server-side request forgery. The attack can be initiated remotely. The exploit has been made available to the public and could be used for attacks. Patch name: 2efbe5d560e7ed9bc5209c203dc4aa6ecdbc7405. To fix this issue, it is recommended to deploy a patch.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-16196 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16196 is a medium-severity server-side request forgery 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-16196 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-16196/ (Markdown: https://insights.sbomify.com/CVE-2026-16196/index.md)
```

## Sources

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

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