# CVE-2026-10216: unitedbyai droidclaw claim Endpoint pairing.ts excessive authentication

> Attackers can bypass authentication rate limits on the claim endpoint, potentially enabling brute-force attacks against the droidclaw server.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jun 2026
- **Updated:** 1 Jun 2026
- **Also known as:** GHSA-g45j-9379-j77g

## What is CVE-2026-10216?

CVE-2026-10216 is a medium-severity vulnerability in unitedbyai droidclaw, published on 1 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was detected in unitedbyai droidclaw up to 0.5.3. The affected element is an unknown function of the file server/src/routes/pairing.ts of the component claim Endpoint. The manipulation results in improper restriction of excessive authentication attempts. The attack may be launched remotely. This attack is characterized by high complexity. The exploitability is described as difficult. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-799 (Improper Control of Interaction Frequency), CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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


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

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

## Is CVE-2026-10216 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10216 is a medium-severity vulnerability in unitedbyai droidclaw, published on 1 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10216 exists.

Affected product: unitedbyai droidclaw. 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-10216/ (Markdown: https://insights.sbomify.com/CVE-2026-10216/index.md)
```

## Sources

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

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