Quick answers
- Is CVE-2026-16119 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-16119 being exploited in the wild.
- How severe is CVE-2026-16119?
- Medium severity, with a CVSS score of 6.3, published 18 July 2026.
- Which products and versions are affected?
- Nextlevelbuilder GoClaw <= 3.13.2.
- Is there a fix for CVE-2026-16119?
- 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-16119 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-16119?
- 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 incorrect authorization vulnerability exists in GoClaw's `RequestApproval` function within `internal/tools/exec_approval.go`. The root cause is a logic flaw in the approval cache where an 'allow-always' decision only persists the base binary name (extracted via `extractBin`) rather than the full command string or execution plan. For multiplexer binaries like BusyBox, approving a single benign command grants permanent trust to the binary itself. A remote attacker with operator-level authentication can exploit this by first getting a benign command approved and subsequently executing arbitrary shell payloads (e.g., `busybox sh -c ...`) without triggering additional approval prompts. This leads to arbitrary command execution with the privileges of the GoClaw process.
Affected products
- nextlevelbuilder GoClaw <= 3.13.2
Timeline
- 2026-07-18: disclosed
- 2026-07-18: advisory