User enumeration via unequal sign-in timing
Published Jun 23, 2026 · Updated Jun 23, 2026
Observable timing discrepancy in NocoDB before 2026.04.1 allows remote attackers to enumerate registered email addresses. The unknown-user branch in auth.service.ts returns without performing the bcrypt password comparison used for known accounts, producing measurably shorter failed sign-ins. Unauthenticated network access to the sign-in endpoint is sufficient; the bounded impact is disclosure of account existence, not account access.
Summary
What happened
Observable timing discrepancy in NocoDB before 2026.04.1 allows remote attackers to enumerate registered email addresses. The unknown-user branch in auth.service.ts returns without performing the bcrypt password comparison used for known accounts, producing measurably shorter failed sign-ins. Unauthenticated network access to the sign-in endpoint is sufficient; the bounded impact is disclosure of account existence, not account access.
The record
- CVE
- CVE-2026-47380
- Published
- Jun 23, 2026
- Updated
- Jun 23, 2026
- Vendor
- NocoDB
- Product
- NocoDB
- Classifications
- CWE-208, CWE-307, T1589.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 23, 2026CVE publishedPublication date reported by the CVE source.
- Jun 23, 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=< 2026.04.1
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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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