Severity by source
AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
Lifecycle Timeline
4DescriptionGitHub Advisory
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.
AnalysisAI
Homarr prior to version 1.57.0 contains a race condition in the user registration endpoint that allows authenticated attackers to bypass single-use invite token restrictions and create multiple user accounts with a single token. The vulnerability stems from non-atomic database operations (CHECK, CREATE, DELETE) that can be exploited through concurrent requests, enabling unauthorized account creation on instances with restrictive registration policies. The issue is patched in version 1.57.0.
Technical ContextAI
The vulnerability exploits a classic race condition (CWE-367) in Homarr's user registration flow at the /api/trpc/user.register endpoint. The application validates invite tokens and creates user accounts through three separate, non-atomic database operations: first checking token validity, then creating the user account, and finally deleting the spent token. Because these operations execute sequentially without transaction isolation, an attacker can submit multiple concurrent registration requests that all pass the validation step before any request reaches the deletion step. This allows the same invite token to satisfy validation checks for multiple accounts simultaneously. The vulnerability requires network-accessible Homarr instances with invitation-based registration enabled and affects the core authentication and account provisioning subsystem.
RemediationAI
Upgrade Homarr to version 1.57.0 or later, which patches the race condition by implementing atomic database transactions for the user registration flow. Organizations unable to upgrade immediately should review invite token distribution practices and consider temporarily disabling invitation-based registration if alternative authentication methods are available. For instances that must remain on pre-1.57.0 versions, implement application-level rate limiting on the /api/trpc/user.register endpoint and consider adding database-level constraints to enforce single-use token semantics at the storage layer. See https://github.com/homarr-labs/homarr/security/advisories/GHSA-vfw3-53q9-2hp8 for additional mitigation guidance from the Homarr security team.
Unauthenticated Server-Side Request Forgery in Homarr versions before 1.54.0 enables remote attackers to initiate arbitr
Unauthenticated attackers can query the integration.all endpoint in Homarr prior to version 1.54.0 to enumerate all conf
DOM-based Cross-Site Scripting in Homarr dashboard versions prior to 1.57.0 allows unauthenticated remote attackers to e
Homarr is an open-source dashboard. Rated high severity (CVSS 8.1), this vulnerability is remotely exploitable, low atta
Homarr versions prior to 1.52.0 contain an unauthenticated SSRF vulnerability in the widget.app.ping endpoint that accep
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-19277