GHSA-cr7p-cr3q-h5cm: Budibase: Account Enumeration via Login Lockout Response Differential
(updated )
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.
References
- github.com/Budibase/budibase/commit/eaae816ab81615c07eb10e4619af078d00e2a706
- github.com/Budibase/budibase/pull/19108
- github.com/Budibase/budibase/releases/tag/3.39.25
- github.com/Budibase/budibase/security/advisories/GHSA-cr7p-cr3q-h5cm
- github.com/advisories/GHSA-cr7p-cr3q-h5cm
- nvd.nist.gov/vuln/detail/CVE-2026-73306
Code Behaviors & Features
Detect and mitigate GHSA-cr7p-cr3q-h5cm with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →