Username enumeration via unequal bcrypt verification timing
Published Apr 16, 2026 · Updated Apr 16, 2026
Observable timing discrepancy in Note Mark 0.19.1 and earlier allows remote attackers to enumerate usernames through login requests. The POST /api/auth/token path runs bcrypt.CompareHashAndPassword only when the queried username exists and otherwise returns without an equivalent bcrypt operation. Network access to the exposed login endpoint is sufficient; repeated response-time measurements disclose account existence and support targeted credential attacks.
Summary
What happened
Observable timing discrepancy in Note Mark 0.19.1 and earlier allows remote attackers to enumerate usernames through login requests. The POST /api/auth/token path runs bcrypt.CompareHashAndPassword only when the queried username exists and otherwise returns without an equivalent bcrypt operation. Network access to the exposed login endpoint is sufficient; repeated response-time measurements disclose account existence and support targeted credential attacks.
The record
- CVE
- CVE-2026-40263
- Published
- Apr 16, 2026
- Updated
- Apr 16, 2026
- Vendor
- Leo Spratt
- Product
- Note Mark
- Classifications
- CWE-208, T1087
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 16, 2026CVE publishedPublication date reported by the CVE source.
- Apr 16, 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=< 0.19.2
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
- GitHub advisory timing-comparison reproductionproof 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