Account enumeration via skipped bcrypt comparison
Published Sep 21, 2026 · Updated Sep 23, 2026
Observable timing discrepancy in Sync-in Server before 2.4.1 allows remote attackers to enumerate valid accounts via login timing. The MySQL validateUser() path returns when findUser() finds no login or email, skipping comparePassword(), while existing accounts incur a bcrypt comparison. The unauthenticated POST /api/auth/login endpoint therefore reveals account validity through response latency, enabling focused credential attacks and phishing.
Summary
What happened
Observable timing discrepancy in Sync-in Server before 2.4.1 allows remote attackers to enumerate valid accounts via login timing. The MySQL validateUser() path returns when findUser() finds no login or email, skipping comparePassword(), while existing accounts incur a bcrypt comparison. The unauthenticated POST /api/auth/login endpoint therefore reveals account validity through response latency, enabling focused credential attacks and phishing.
The record
- CVE
- CVE-2026-58272
- Published
- Sep 21, 2026
- Updated
- Sep 23, 2026
- Vendor
- Sync-in
- Product
- Sync-in Server
- Classifications
- CWE-208, CAPEC-541, CAPEC-462, CAPEC-580, T1087
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 21, 2026CVE publishedPublication date reported by the CVE source.
- Sep 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=< 2.4.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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- GHSA login timing 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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started