Authentication Bypass in Sipeed PicoClaw (CVE-2026-16198)
Summary
Authentication bypass in Sipeed PicoClaw (CVE-2026-16198). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
A vulnerability was detected in Sipeed PicoClaw up to 0.2.9. The impacted element is an unknown function of the file web/backend/middleware/access_control.go of the component First Run Setup. Performing a manipulation of the argument allowed_cidrs results in authentication bypass using alternate channel. The attack may be initiated remotely. The attack's complexity is rated as high. The exploitability is regarded as difficult. The exploit is now public and may be used. The patch is named 017601354be38cb027ff3ffb01aed79bd5d12610. Applying a patch is the recommended action to fix this issue.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-16198 has been found in Sipeed PicoClaw.
Risk of unauthorized operations or information disclosure. CVSS score: 5.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Sipeed PicoClaw CVE-2026-16198" on the vendor's site.
CVE-2026-16198 (Sipeed PicoClaw) — CWE-287 / CVSS v3 5.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Authentication bypass (CWE-287) exists in Sipeed PicoClaw.
Check the vendor advisory for the affected versions of Sipeed PicoClaw.
Severity: Medium (CVSS 5.6/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Sipeed PicoClaw を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory nvd.nist.gov
- advisory vuldb.com
- advisory vuldb.com
- advisory vuldb.com
- advisory github.com
- patch github.com
- patch github.com
- report github.com
- report vuldb.com
- web github.com
- web github.com
- web github.com