CVE-2026-47784 is an observable timing discrepancy in Memcached versions before 1.6.42 during SASL password-database authentication. The sasl_server_userdb_checkpass password-verification logic uses memcmp, whose execution time can vary according to the extent of matching password data. An unauthenticated remote party may measure authentication response times over repeated attempts to infer password bytes incrementally.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A timing side-channel vulnerability in memcached SASL password-database authentication caused by non-constant-time password comparison using memcmp.
A high-severity timing side-channel vulnerability in Memcached SASL password verification that can enable attackers to infer passwords byte by byte through timing analysis in versions before 1.6.42.
A timing side-channel vulnerability in memcached before 1.6.42 affecting SASL password database authentication due to use of memcmp in sasl_server_userdb_checkpass.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.