Quick answers
- Is CVE-2026-16121 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-16121 being exploited in the wild.
- How severe is CVE-2026-16121?
- 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-16121?
- 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-16121 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-16121?
- 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
An improper authorization vulnerability exists in GoClaw's `ExecApprovalManager.CheckCommand` function within `internal/tools/exec_approval.go`. When `tools.execApproval.security` is set to 'full' and `ask` is set to 'on-miss', the system auto-approves commands based solely on the binary's basename if it exists in a hardcoded `safeBins` list. Because the logic fails to inspect command-line arguments, binaries like `sort` (using `-o` for file writes) and `grep` (using `-R` for recursive directory reads) can be used to perform unauthorized file operations. An authenticated attacker with 'Operator' privileges can trigger this remotely via the `POST /v1/tools/invoke` endpoint to bypass the human-in-the-loop approval requirement.
Affected products
- nextlevelbuilder GoClaw up to 3.13.2
Timeline
- 2026-07-18: disclosed: Vulnerability reported and published via VulDB and NVD.