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.
CVE-2026-16198
Score 5.6 from GitHub Security Advisory (severity: LOW) published 2026-07-19. a secondary CVSS source baseline 5.6; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.6
- EG Score
- 5.6(high)
- EG Risk
- 41(Track)EG Risk 41/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity56% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 45.4%
- KEV
- Not listed
Published
July 18, 2026
Last Modified
July 21, 2026
Advisory Details (4)
Auto-updated Jul 19, 2026GitHub - sipeed/picoclaw: Tiny, Fast, and Deployable anywhere — automate the mundane, unleash your creativity · GitHub
https://github.com/sipeed/picoclaw/commit 017601354be3 (sipeed/picoclaw)
Fix landed in sipeed/picoclaw commit 017601354be3 — awaiting tagged release
https://github.com/sipeed/picoclaw/commit/017601354be38cb027ff3ffb01aed79bd5d12610feat(web): harden launcher access control
Fix merged in sipeed/picoclaw PR #3083 on 2026-06-11 — awaiting tagged release
https://github.com/sipeed/picoclaw/pull/3083[Security] PicoClaw launcher `allowed_cidrs` can be bypassed through same-host loopback proxying during first-run setup · Issue #3080 · sipeed/picoclaw · GitHub
https://github.com/sipeed/picoclaw/issues/3080Vendor Advisories for CVE-2026-16198(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 17× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:05 UTCEG score recompute
- 2026-07-22 23:56 UTCEG score recompute
- 2026-07-22 23:56 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCNVD updateCVSS v4 → 2.9
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-21 14:37 UTCMITRE cvelistV5CVSS v4 → 6.3
- 2026-07-20 17:50 UTCEG score recompute
- 2026-07-20 17:50 UTCGHSA enrichment
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 02:06 UTCEG score recompute
- 2026-07-19 02:06 UTCGHSA enrichment
- 2026-07-19 02:05 UTCNVD updateCVSS v4 → 2.9
- 2026-07-18 23:50 UTCEG score recompute
- 2026-07-18 23:49 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-16198?
When was CVE-2026-16198 disclosed?
Is CVE-2026-16198 actively exploited?
What is the CVSS score of CVE-2026-16198?
How do I remediate CVE-2026-16198?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16198
Is Your Infrastructure Affected by CVE-2026-16198?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.