Username enumeration via SASL timing discrepancy
Published May 20, 2026 · Updated May 20, 2026
Observable timing discrepancy in Memcached memcached before 1.6.42 allows remote attackers to enumerate valid SASL usernames. sasl_server_userdb_checkpass exits its password-file loop when a username matches, making valid-name requests measurably faster than full scans. Exploitation requires network access to a server using SASL password-database authentication and repeated timing measurements; it reveals username validity, not passwords or cache data.
Summary
What happened
Observable timing discrepancy in Memcached memcached before 1.6.42 allows remote attackers to enumerate valid SASL usernames. sasl_server_userdb_checkpass exits its password-file loop when a username matches, making valid-name requests measurably faster than full scans. Exploitation requires network access to a server using SASL password-database authentication and repeated timing measurements; it reveals username validity, not passwords or cache data.
The record
- CVE
- CVE-2026-47783
- Published
- May 20, 2026
- Updated
- May 20, 2026
- Vendor
- Memcached
- Product
- memcached
- Classifications
- CWE-208, T1087
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 20, 2026CVE publishedPublication date reported by the CVE source.
- May 20, 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 <1.6.42
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
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