Quick answers
- Is CVE-2026-16123 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-16123 being exploited in the wild.
- How severe is CVE-2026-16123?
- Medium severity, with a CVSS score of 6.3, published 18 July 2026.
- Which products and versions are affected?
- Nextlevelbuilder GoClaw up to 3.13.2.
- Is there a fix for CVE-2026-16123?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-16123 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-16123?
- Check whether you run Nextlevelbuilder GoClaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A missing authorization vulnerability exists in GoClaw up to version 3.13.2 within the ToolsInvokeHandler.ServeHTTP function located in internal/http/tools_invoke.go. The handler accepts an attacker-controlled agentId and injects it into the request context without performing a CanAccess check, unlike other agent-related endpoints. When the 'cron' tool is invoked via POST /v1/tools/invoke, this unauthorized agent ID is persisted in the database. The scheduler subsequently trusts this stored binding, allowing a user with operator.write privileges to execute tasks against foreign agents. A public exploit demonstrating this stored authorization bypass has been disclosed.
Affected products
- nextlevelbuilder GoClaw up to 3.13.2
Timeline
- 2026-07-18: disclosed: Vulnerability details and PoC made public via GitHub and VulDB
- 2026-07-18: advisory: CVE-2026-16123 published