Quick answers
- Is CVE-2026-15626 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-15626 being exploited in the wild.
- How severe is CVE-2026-15626?
- Medium severity, with a CVSS score of 6.3, published 14 July 2026.
- Which products and versions are affected?
- Nextlevelbuilder GoClaw 3.13.3-beta.3.
- Is there a fix for CVE-2026-15626?
- 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-15626 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-15626?
- 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 path traversal vulnerability exists in the `writeFile` function within `internal/providers/acp/tool_bridge.go` of GoClaw. The root cause is a flaw in `resolvePath()` where `filepath.EvalSymlinks` is used for validation; if the function fails (e.g., on a dangling symlink), the code falls back to a lexical path check. An attacker can exploit this by first creating a dangling symlink pointing to a sensitive host location and then calling `fs/writeTextFile` on that path. Because the lexical check passes while the subsequent `os.WriteFile` follows the symlink, the attacker can write arbitrary content outside the sandbox. This requires the ability to issue ACP tool requests, typically available to an authenticated agent session.
Affected products
- nextlevelbuilder GoClaw 3.13.3-beta.3
Timeline
- 2026-07-14: disclosed: Vulnerability disclosed and CVE assigned