Account enumeration via login lockout response differential
Published Aug 12, 2026 · Updated Aug 12, 2026
Observable response discrepancy in Budibase before 3.39.25 allows remote attackers to enumerate valid email addresses through login failures. The login handler increments failure counters only for existing users, while emailLockout returns distinctive lockout headers only for identifiers whose counters reach the threshold. Unauthenticated access to a tenant login endpoint is sufficient; repeated failures disclose account validity and lock each valid account for 15 minutes.
Summary
What happened
Observable response discrepancy in Budibase before 3.39.25 allows remote attackers to enumerate valid email addresses through login failures. The login handler increments failure counters only for existing users, while emailLockout returns distinctive lockout headers only for identifiers whose counters reach the threshold. Unauthenticated access to a tenant login endpoint is sufficient; repeated failures disclose account validity and lock each valid account for 15 minutes.
The record
- CVE
- CVE-2026-73306
- Published
- Aug 12, 2026
- Updated
- Aug 12, 2026
- Vendor
- Budibase
- Product
- Budibase
- Classifications
- CWE-204, T1087
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 12, 2026CVE publishedPublication date reported by the CVE source.
- Aug 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.39.25
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Vendor advisory login-lockout proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo