CVE-2026-44443: CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') in prolix-oc Lumiverse
Lumiverse is a full-featured AI chat application. Prior to 0.9.7, consumeNonce() only checks that the module-level variable is set and unexpired. It does not validate any value from the incoming HTTP request or bind the nonce to the admin's session. If the admin's auth.api.signUpEmail() call fails before the before hook fires (e.g. BetterAuth rejects a duplicate email at the validation layer), the nonce is set but never consumed. Any POST /api/auth/sign-up/email request that arrives during the remaining window registers successfully regardless of who sent it. An attacker who can observe or predict when the admin is creating users (must be a dupplicate user) can race the 10-second window to register an unauthorized account. This vulnerability is fixed in 0.9.7.
AI Analysis
Technical Summary
Lumiverse, an AI chat application by prolix-oc, had a race condition vulnerability (CWE-362) in versions before 0.9.7 related to nonce handling during user sign-up. The consumeNonce() function did not validate the nonce against the request or bind it to the admin session, allowing an attacker to exploit a 10-second window after a failed admin sign-up attempt to register unauthorized accounts by racing the nonce consumption. This improper synchronization of shared resources could lead to unauthorized account creation. The vulnerability is addressed in Lumiverse version 0.9.7.
Potential Impact
An attacker who can observe or predict when an admin is creating users and trigger a duplicate user validation failure can exploit the race condition to register unauthorized accounts within a 10-second window. This can lead to unauthorized access or privilege escalation through fraudulent account creation. The impact is limited to confidentiality and integrity with no reported availability impact. The CVSS score of 4.8 reflects a medium severity risk.
Mitigation Recommendations
This vulnerability is fixed in Lumiverse version 0.9.7. Users should upgrade to version 0.9.7 or later to remediate this issue. No official patch or workaround details are provided beyond upgrading. Until upgraded, administrators should be aware of the risk during user sign-up processes involving duplicate email validation failures.
CVE-2026-44443: CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') in prolix-oc Lumiverse
Description
Lumiverse is a full-featured AI chat application. Prior to 0.9.7, consumeNonce() only checks that the module-level variable is set and unexpired. It does not validate any value from the incoming HTTP request or bind the nonce to the admin's session. If the admin's auth.api.signUpEmail() call fails before the before hook fires (e.g. BetterAuth rejects a duplicate email at the validation layer), the nonce is set but never consumed. Any POST /api/auth/sign-up/email request that arrives during the remaining window registers successfully regardless of who sent it. An attacker who can observe or predict when the admin is creating users (must be a dupplicate user) can race the 10-second window to register an unauthorized account. This vulnerability is fixed in 0.9.7.
CVSS v3.1
Score 4.8medium
Affected software
pkg:github/prolix-oc/LumiverseRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Lumiverse, an AI chat application by prolix-oc, had a race condition vulnerability (CWE-362) in versions before 0.9.7 related to nonce handling during user sign-up. The consumeNonce() function did not validate the nonce against the request or bind it to the admin session, allowing an attacker to exploit a 10-second window after a failed admin sign-up attempt to register unauthorized accounts by racing the nonce consumption. This improper synchronization of shared resources could lead to unauthorized account creation. The vulnerability is addressed in Lumiverse version 0.9.7.
Potential Impact
An attacker who can observe or predict when an admin is creating users and trigger a duplicate user validation failure can exploit the race condition to register unauthorized accounts within a 10-second window. This can lead to unauthorized access or privilege escalation through fraudulent account creation. The impact is limited to confidentiality and integrity with no reported availability impact. The CVSS score of 4.8 reflects a medium severity risk.
Mitigation Recommendations
This vulnerability is fixed in Lumiverse version 0.9.7. Users should upgrade to version 0.9.7 or later to remediate this issue. No official patch or workaround details are provided beyond upgrading. Until upgraded, administrators should be aware of the risk during user sign-up processes involving duplicate email validation failures.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-06T15:49:25.191Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a16041ae29bf47b505e9f2e
Added to database: 05/26/2026, 20:35:38 UTC
Last enriched: 06/02/2026, 21:01:23 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 60
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.