A security flaw has been discovered in Sipeed PicoClaw up to 0.2.9. This affects the function webhook.ParseRequest of the file pkg/channels/line/line.go of the component LINE Webhook. The manipulation results in authentication bypass by capture-replay. The attack may be launched remotely. The exploit has been released to the public and may be used for attacks. The reported GitHub issue was closed automatically with the label "not planned" by a bot.
CVE-2026-16083
Score 5.3 from GitHub Security Advisory published 2026-07-18. a secondary CVSS source baseline 5.3; 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.3
- EG Score
- 5.3(high)
- EG Risk
- 55(Attend)EG Risk 55/100SSVC: Attend
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 computedSeverity53% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS
- 35.1%
- KEV
- Not listed
Published
July 18, 2026
Last Modified
July 20, 2026
Advisory Details (2)
Auto-updated Jul 19, 2026[Security] Signed LINE webhook replay allows duplicate inbound event execution in PicoClaw · Issue #3073 · sipeed/picoclaw · GitHub
https://github.com/sipeed/picoclaw/issues/3073GitHub - sipeed/picoclaw: Tiny, Fast, and Deployable anywhere — automate the mundane, unleash your creativity · GitHub
https://github.com/sipeed/picoclaw/Vendor Advisories for CVE-2026-16083(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 16× in last 7d / 16× 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 03:05 UTCEG score recompute
- 2026-07-23 00:10 UTCEG score recompute
- 2026-07-23 00:10 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 18:40 UTCNVD updateCVSS v4 → 5.5
- 2026-07-20 17:57 UTCMITRE cvelistV5CVSS v4 → 6.9
- 2026-07-20 17:54 UTCEG score recompute
- 2026-07-20 17:54 UTCGHSA enrichment
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-18 10:05 UTCEG score recompute
- 2026-07-18 10:05 UTCGHSA enrichment
- 2026-07-18 10:02 UTCNVD updateCVSS v4 → 5.5
- 2026-07-18 08:34 UTCEG score recompute
- 2026-07-18 08:34 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-16083?
When was CVE-2026-16083 disclosed?
Is CVE-2026-16083 actively exploited?
What is the CVSS score of CVE-2026-16083?
How do I remediate CVE-2026-16083?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16083
Is Your Infrastructure Affected by CVE-2026-16083?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.