Is CVE-2026-10217 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-10217 being exploited in the wild.

How severe is CVE-2026-10217?

Medium severity, with a CVSS score of 6.3, published 1 June 2026.

Which products and versions are affected?

nextlevelbuilder GoClaw <= 3.11.3.

Is there a fix for CVE-2026-10217?

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-10217 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-10217?

Check whether anything you run is named in the advisory. 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.

CVE-2026-10217: nextlevelbuilder GoClaw improper privilege management in RoleAdmin Gateway

Q: Is there a fix for CVE-2026-10217?

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.

Q: How is CVE-2026-10217 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-10217?

Check whether anything you run is named in the advisory. 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.

CVE-2026-10217 · Severity: medium · CVSS 6.3 · Published 2026-06-01

A security flaw in GoClaw, an AI agent platform, allows users with low-level 'Viewer' permissions to perform administrative actions. An attacker could exploit this to modify critical system settings, such as Text-to-Speech (TTS) configurations or storage files, which are normally restricted to owners and admins. This could lead to service disruptions, unauthorized data modification, or the redirection of system traffic to malicious servers.

Quick answers

Is CVE-2026-10217 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-10217 being exploited in the wild.
How severe is CVE-2026-10217?: Medium severity, with a CVSS score of 6.3, published 1 June 2026.
Which products and versions are affected?: nextlevelbuilder GoClaw <= 3.11.3.
Is there a fix for CVE-2026-10217?: 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-10217 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-10217?: Check whether anything you run is named in the advisory. 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 broken access control vulnerability exists in GoClaw's RoleAdmin Gateway component due to improper privilege management in the handleSave function within internal/http/tts_config.go and the handleDelete function in internal/http/storage.go. While the requireAuth middleware verifies global privileges, the resolveAuthWithBearer function incorrectly assigns the RoleAdmin system permission to any valid tenant member when authenticating via a Web Gateway Token. Because these specific endpoints lack a secondary requireTenantAdmin() check, an authenticated user with 'Viewer' permissions can spoof administrative actions. This allows for unauthorized modification of TTS configurations (potentially leading to SSRF) and unauthorized file operations in storage. A public exploit script has been released.

Affected products

nextlevelbuilder GoClaw <= 3.11.3

Timeline

2026-05-07: disclosed: Issue reported on GitHub repository
2026-06-01: advisory: CVE published by VulDB/NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.