CVE-2026-47783
Memcached vulnerability analysis and mitigation

Overview

CVE-2026-47783 is a timing side-channel vulnerability in memcached's SASL password database authentication that allows unauthenticated remote attackers to enumerate valid usernames. It affects all memcached versions before 1.6.42 and was disclosed on May 20, 2026, with the fix committed on May 18, 2026. The vulnerability carries a CVSS v3.1 base score of 8.1 (High) (Github Advisory, Feedly).

Technical details

The root cause is classified as CWE-208 (Observable Timing Discrepancy). In sasl_server_userdb_checkpass() within sasl_defs.c, the authentication loop broke out early (break) as soon as a matching username was found in the password file, creating a measurable timing difference between valid and invalid usernames. Additionally, the password comparison used the standard memcmp() function, which returns on the first differing byte, potentially leaking password bytes through timing analysis. The fix removes the early break so the entire file is always scanned, clears the buffer to zero before each fgets() call, and replaces memcmp() with a constant-time safe_memcmp() for both username and password comparisons (Memcached Commit, Github Advisory).

Impact

An unauthenticated network attacker can exploit the timing discrepancy to enumerate valid SASL usernames on memcached instances configured with SASL password database authentication. Successful username enumeration reduces the effort required for subsequent credential-stuffing or brute-force attacks against the memcached service, potentially leading to unauthorized access with high confidentiality, integrity, and availability impact. The vulnerability is limited in scope to instances using SASL userdb authentication and does not directly enable code execution or data exfiltration on its own (Github Advisory, Feedly).

Exploitation steps

  1. Reconnaissance: Identify memcached instances with SASL authentication enabled (typically on TCP port 11211) using network scanners such as Shodan, Censys, or nmap. Confirm the target is running memcached before version 1.6.42.
  2. Establish baseline timing: Send SASL authentication requests with known-invalid usernames and measure the response time to establish a baseline for "username not found" responses.
  3. Username enumeration via timing: Iteratively send SASL authentication requests with candidate usernames (e.g., from a wordlist). A statistically shorter or longer response time compared to the baseline indicates the username exists in the password database, as the vulnerable loop exits early upon finding a match.
  4. Statistical analysis: Repeat each candidate username multiple times and average the response times to reduce network jitter noise, improving the reliability of the timing oracle.
  5. Credential attack: Use the enumerated valid usernames as input for targeted brute-force or credential-stuffing attacks against the memcached SASL endpoint to attempt full authentication (Memcached Commit, Github Advisory).

Indicators of compromise

  • Network: High volume of SASL authentication attempts from a single source IP to memcached port 11211, particularly with many different usernames and repeated attempts per username; unusual patterns of authentication failures with varying response latencies.
  • Logs: Memcached authentication logs showing repeated failed SASL login attempts with a wide variety of usernames from the same source; authentication attempts at a rate inconsistent with normal application behavior.
  • Process/Behavior: Anomalous connection patterns to memcached from hosts that are not recognized application servers; connections from external or unexpected IP ranges if memcached is inadvertently exposed to the internet.

Mitigation and workarounds

Upgrade memcached to version 1.6.42 or later, which replaces the vulnerable memcmp()-based comparisons with constant-time safe_memcmp() and removes the early loop exit in sasl_server_userdb_checkpass() (Memcached Release Notes, Memcached Commit). If immediate patching is not possible, restrict network access to memcached instances using firewall rules so only trusted application servers can connect, and implement rate limiting on authentication attempts. Downstream distributions including SUSE, openSUSE, Amazon Linux 2023, Debian, Ubuntu, and cPanel EasyApache4 have released updated packages (cPanel Advisory, SUSE Advisory).

Community reactions

The vulnerability received coverage from multiple security news outlets including GBHackers, CyberSecurityNews, SecurityOnline, and CyberPress, generally characterizing it as a high-severity flaw enabling remote username enumeration (GBHackers, CyberSecurityNews). The Hacker News weekly recap also mentioned the vulnerability in the context of notable security issues (THN Recap). The memcached maintainer noted in the 1.6.42 release notes that this was a major security-focused release and strongly advised upgrading, while also observing that many submitted security reports in this round overstated severity (Memcached Release Notes). The CVE appeared in Reddit's CVEWatch trending lists for late May 2026, indicating moderate community interest.

Additional resources


SourceThis report was generated using AI

Related Memcached vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2023-46853CRITICAL9.8
  • Memcached logoMemcached
  • memcached-debuginfo
NoYesOct 27, 2023
CVE-2026-47784HIGH8.1
  • Memcached logoMemcached
  • memcached
NoYesMay 20, 2026
CVE-2026-47783HIGH8.1
  • Memcached logoMemcached
  • memcached
NoYesMay 20, 2026
CVE-2023-46852HIGH7.5
  • Memcached logoMemcached
  • memcached-selinux
NoYesOct 27, 2023
CVE-2026-24809MEDIUM6.9
  • Memcached logoMemcached
  • ntopng
NoYesJan 27, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management