Umami up to 3.4.x Two-Factor Authentication /api/2fa/verify recordFailedAttempt race condition
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00+ |
Summary
A vulnerability identified as critical has been detected in Umami up to 3.4.x. The impacted element is the function recordFailedAttempt of the file /api/2fa/verify of the component Two-Factor Authentication. Performing a manipulation results in race condition.
This vulnerability is known as CVE-2026-134829. Remote exploitation of the attack is possible. No exploit is available.
You should upgrade the affected component.
Details
A vulnerability was found in Umami up to 3.4.x. It has been classified as critical. This affects the function recordFailedAttempt of the file /api/2fa/verify of the component Two-Factor Authentication. The manipulation with an unknown input leads to a race condition vulnerability. CWE is classifying the issue as CWE-362. The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Umami 3.3.0 before 3.5.0 contains a race condition in two-factor authentication attempt limiting that allows attackers holding a user's password to bypass lockout. Attackers can send many concurrent POST requests to /api/2fa/verify that pass checkRateLimit before recordFailedAttempt runs, brute-forcing TOTP or backup codes beyond the five-attempt limit.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-134829 since 11/22/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available.
Upgrading to version 3.5.0 eliminates this vulnerability. Applying the patch 9411f67d7e37d149a40eef016022ed5fe5c6671d is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.8
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Race conditionCWE: CWE-362
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Umami 3.5.0
Patch: 9411f67d7e37d149a40eef016022ed5fe5c6671d
Timeline
11/22/2026 Advisory disclosed11/22/2026 CVE reserved
11/22/2026 VulDB entry created
11/22/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CNA: VulnCheck
CVE: CVE-2026-134829 (🔒)
GCVE (CVE): GCVE-0-2026-134829
GCVE (VulDB): GCVE-100-442185
Entry
Created: 11/22/2026 22:39Changes: 11/22/2026 22:39 (78)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.