# CVE-2026-10616: nextlevelbuilder GoClaw Team Task Completion team_tasks_lifecycle.go TeamTasksTool.executeComplete authorization

> Remote attackers can bypass authorization in GoClaw's team task completion handler to perform unauthorized actions.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jun 2026
- **Updated:** 3 Jun 2026
- **Also known as:** GHSA-cq6h-h9c3-mq74

## What is CVE-2026-10616?

CVE-2026-10616 is a medium-severity missing authorization vulnerability in nextlevelbuilder GoClaw, published on 2 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A weakness has been identified in nextlevelbuilder GoClaw up to 3.11.3. The impacted element is the function TeamTasksTool.executeComplete of the file internal/tools/team_tasks_lifecycle.go of the component Team Task Completion Handler. Executing a manipulation can lead to missing authorization. The attack may be launched remotely. The exploit has been made available to the public and could be used for attacks. The project tagged the reported issue as bug.

Weakness: CWE-863 (Incorrect Authorization), CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-10616?


## How do I fix CVE-2026-10616?

No fix has been published for CVE-2026-10616 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-10616 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10616 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10616 and fix it if it is affected.

What it is: CVE-2026-10616 is a medium-severity missing authorization vulnerability in nextlevelbuilder GoClaw, published on 2 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10616 exists.

Affected product: nextlevelbuilder GoClaw. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10616/ (Markdown: https://insights.sbomify.com/CVE-2026-10616/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10616
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10616
- OSV: https://osv.dev/vulnerability/CVE-2026-10616

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10616/
Summaries are generated and may contain mistakes; the official description above is the record.