Skip to main content
VulnerabilityPublished

CVE-2026-32602: homarr · Time-of-check Time-of-use (TOCTOU) Race Condition

Affects homarrSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.2 Medium : upgrade to 1.57.0 when convenient.

Data as of 30 Oct 2026, 11:34 UTC

CVSS 3.1 base score
4.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.57.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade homarr and homarr-labs/homarr to 1.57.0.

Affected software

ProductAffectedFixed in
homarr-labshomarrAffected
  • <1.57.0
Fixed in
  • 1.57.0
GitHubhomarr-labs/homarrpkg:github/homarr-labs/homarrOther threatsAffected
  • <1.57.0
Fixed in
  • 1.57.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade homarr to version 1.57.0 or later, where this race condition vulnerability is fixed. Since the fix involves making the registration process atomic, applying this official update fully mitigates the issue. Patch status is confirmed by the vendor's versioning information. No additional mitigations are indicated.

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.

References

Community reviews

Loading reviews…