# CVE-2026-7505: nextlevelbuilder GoClaw/GoClaw Lite RPC improper authorization


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Apr 2026
- **Updated:** 1 May 2026
- **Also known as:** GHSA-p2qq-m885-cm42

## What is CVE-2026-7505?

CVE-2026-7505 is a medium-severity vulnerability in nextlevelbuilder GoClaw, published on 30 Apr 2026. 

### Official description

A flaw has been found in nextlevelbuilder GoClaw and GoClaw Lite up to 3.8.5. This affects an unknown function of the component RPC Handler. This manipulation causes improper authorization. The attack may be initiated remotely. The exploit has been published and may be used. Upgrading to version 3.9.0 mitigates this issue. Patch name: 406022e79f4a18b3070a446712080571eff11e30. You should upgrade the affected component.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-7505 being exploited?

There is no known exploitation of CVE-2026-7505 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7505 is a medium-severity vulnerability in nextlevelbuilder GoClaw, published on 30 Apr 2026. 
Exploitation: There is no known exploitation of CVE-2026-7505 in the wild and no public exploit code.

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-7505/ (Markdown: https://insights.sbomify.com/CVE-2026-7505/index.md)
```

## Sources

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

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