Quick answers
- Is CVE-2026-16120 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-16120 being exploited in the wild.
- How severe is CVE-2026-16120?
- Medium severity, with a CVSS score of 6.3, published 18 July 2026.
- Which products and versions are affected?
- Nextlevelbuilder GoClaw <= 3.13.3-beta.3.
- Is there a fix for CVE-2026-16120?
- 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-16120 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-16120?
- 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 vulnerability exists in GoClaw's `internal/tools/exec_approval.go` within the `matchesAllowlist` and `extractBin` functions. When `tools.execApproval.security` is set to `allowlist`, the system uses `filepath.Base()` to extract the command name for validation. This creates an identity split where the approval layer validates a basename (e.g., 'echo'), but the execution layer runs the original user-supplied string (e.g., './echo') via `/bin/sh -c`. An authenticated operator can exploit this by placing a malicious binary with a trusted name in their workspace and invoking it via the `POST /v1/tools/invoke` endpoint. This results in arbitrary command execution with the privileges of the GoClaw host process.
Affected products
- nextlevelbuilder GoClaw <= 3.13.3-beta.3
Timeline
- 2026-07-18: disclosed: Public disclosure of the vulnerability and exploit details.
- 2026-07-18: advisory