All vulnerabilities

Servers and applications

CVE-2026-73306

Account Enumeration via Login Lockout Response Differential in Budibase

Severity
Medium 5.3
Published
22 Jul 2026
Last changed
12 Aug 2026
Added to UpHeron
3 Nov 2026
Fixed in
3.40.0
Exploit chance
0.4% in the next 30 daysHigher than 38% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Response discrepancy (CWE-204)
Attack
Over the network · No login needed · No user action needed
Attacker can
Read some data
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Also known as
GHSA-cr7p-cr3q-h5cm
Sources
Project advisories (GitHub)

Description

The login lockout mechanism in Budibase creates an observable response discrepancy that allows unauthenticated attackers to enumerate valid email addresses. When an existing user's account is locked after 5 failed login attempts, the server returns a distinct 403 response with X-Account-Locked: 1 and Retry-After: 900 headers plus the message "Account temporarily locked." For non-existing users, the response is always a generic 403 "Unauthorized" regardless of attempt count, because the lockout counter is never incremented.

The vulnerability exists in two files that implement the login lockout feature:

packages/worker/src/middleware/lockout.ts:18-36 — The lockout middleware only blocks requests for users that exist in the database AND are locked:

packages/worker/src/api/controllers/global/auth.ts:127-141 — The login handler only increments the failure counter for existing users:

From Budibase/budibase's security advisory. Shortened; the full text is there.

Affected software

SoftwareAffected versions
BudibaseServers and applications · github:budibase/budibase
  • Every version before 3.40.0

About Budibase

low-code development platform

From Wikidata, CC0 1.0.
Docker Hub pulls
2,327,272Docker Hub, 15 Nov 2026
GitHub stars
28,419GitHub, 15 Nov 2026
Forks
2,238GitHub, 15 Nov 2026
Latest release
v4.0.0GitHub, 15 Nov 2026
Released
10 Nov 2026GitHub
First published on GitHub
7 Jun 2019GitHub

References