# CVE-2026-32602: Homarr has a Race Condition in Invite Token Registration (TOCTOU)

> Attackers can create multiple user accounts from a single invite token due to a race condition in the registration endpoint, bypassing single-use restrictions.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **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:** 6 Apr 2026
- **Updated:** 6 Apr 2026
- **Also known as:** GHSA-vfw3-53q9-2hp8

## What is CVE-2026-32602?

CVE-2026-32602 is a medium-severity vulnerability in homarr-labs homarr, published on 6 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Homarr is an open-source dashboard. Prior to 1.57.0, the user registration endpoint (/api/trpc/user.register) is vulnerable to a race condition that allows an attacker to create multiple user accounts from a single-use invite token. The registration flow performs three sequential database operations without a transaction: CHECK, CREATE, and DELETE. Because these operations are not atomic, concurrent requests can all pass the validation step (1) before any of them reaches the deletion step (3). This allows multiple accounts to be registered using a single invite token that was intended to be single-use. This vulnerability is fixed in 1.57.0.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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

It affects 1 product.


Products: Homarr Homarr.

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

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

## Is CVE-2026-32602 being exploited?

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

## Other vulnerabilities in homarr-labs homarr

- [CVE-2026-33510](https://insights.sbomify.com/CVE-2026-33510/): DOM-Based XSS in Homarr /auth/login Redirect (high 8.8)
- [CVE-2025-64759](https://insights.sbomify.com/CVE-2025-64759/): Homarr is Vulnerable to Stored Cross-Site Scripting (XSS) and Possible Privilege Escalation via Malicious SVG Upload (high 8.1)
- [CVE-2025-67493](https://insights.sbomify.com/CVE-2025-67493/): Homarr: missing input sanitization and possible privilege escalation through ldap search query injection (high 7.5)
- [CVE-2026-27796](https://insights.sbomify.com/CVE-2026-27796/): Homarr: Unauthenticated Information Disclosure (Integration Metadata Leak) (medium 5.3)
- [CVE-2026-27797](https://insights.sbomify.com/CVE-2026-27797/): Homarr: Unauthenticated SSRF in rssFeed.ts (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-32602 is a medium-severity vulnerability in homarr-labs homarr, published on 6 Apr 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-32602 exists.

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

## Sources

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

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