A vulnerability was found in nextlevelbuilder GoClaw up to 3.13.2. This affects the function RequestApproval of the file internal/tools/exec_approval.go of the component WebSocket Approval Endpoint. Performing a manipulation results in incorrect authorization. The attack is possible to be carried out remotely. The exploit has been made public and could be used.
CVE-2026-16119
Score 6.3 from GitHub Security Advisory (severity: LOW) published 2026-07-18. a secondary CVSS source baseline 6.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
- 6.3
- EG Score
- 6.3(high)
- EG Risk
- 44(Track)EG Risk 44/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 computedSeverity63% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 20.5%
- KEV
- Not listed
Published
July 18, 2026
Last Modified
July 21, 2026
Advisory Details (3)
Auto-updated Jul 18, 2026GitHub - nextlevelbuilder/goclaw: GoClaw - GoClaw is OpenClaw rebuilt in Go — with multi-tenant isolation, 5-layer security, and native concurrency. Deploy AI agent teams at scale without compromising on safety. · GitHub
https://github.com/nextlevelbuilder/goclaw/[Security] BusyBox-wrapped `allow-always` approval reuses trust across different shell payloads and bypasses exec re-approval · Issue #1212 · nextlevelbuilder/goclaw · GitHub
https://github.com/nextlevelbuilder/goclaw/issues/1212#issuecomment-4760281066[Security] BusyBox-wrapped `allow-always` approval reuses trust across different shell payloads and bypasses exec re-approval · Issue #1212 · nextlevelbuilder/goclaw · GitHub
https://github.com/nextlevelbuilder/goclaw/issues/1212Vendor Advisories for CVE-2026-16119(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 / 19× 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-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:05 UTCEG score recompute
- 2026-07-23 00:08 UTCEG score recompute
- 2026-07-23 00:08 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-21 04:38 UTCNVD updateCVSS v4 → 2.1
- 2026-07-21 03:31 UTCMITRE cvelistV5CVSS v4 → 5.3
- 2026-07-20 17:53 UTCEG score recompute
- 2026-07-20 17:53 UTCGHSA enrichment
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-18 16:08 UTCEG score recompute
- 2026-07-18 16:08 UTCGHSA enrichment
- 2026-07-18 16:03 UTCNVD updateCVSS v4 → 2.1
- 2026-07-18 13:41 UTCEG score recompute
- 2026-07-18 13:39 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-16119?
When was CVE-2026-16119 disclosed?
Is CVE-2026-16119 actively exploited?
What is the CVSS score of CVE-2026-16119?
How do I remediate CVE-2026-16119?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16119
Is Your Infrastructure Affected by CVE-2026-16119?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.