Memcached vulnerabilitiesRanked by how likely they are to be used.

Product80 versions
The short answer

Memcached is made by Memcached. We track 19 published vulnerabilities in it, across 80 versions. None of them is on the list of flaws known to be exploited today. If you run Memcached, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Memcached vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Memcached's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Memcached flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 88%

    Memcached version 1.5.5 contains an Insufficient Control of Network Message Volume (Network Amplification, CWE-406) vulnerability in the UDP support of the memcached server that can result in denial of service via...

    CVSS7.5Published5 Mar 2018
  2. 46%

    An integer overflow in process_bin_sasl_auth function in Memcached, which is responsible for authentication commands of Memcached binary protocol, can be abused to cause heap overflow and lead to remote code execution.

    CVSS8.1Published6 Jan 2017
  3. 28%

    Memcached 1.6.x before 1.6.2 allows remote attackers to cause a denial of service (daemon crash) via a crafted binary protocol header to try_read_command_binary in memcached.c.

    CVSS7.5Published24 Mar 2020
  4. 23%

    An integer overflow in the process_bin_append_prepend function in Memcached, which is responsible for processing multiple commands of Memcached binary protocol, can be abused to cause heap overflow and lead to remote...

    CVSS9.8Published6 Jan 2017
  5. 20%

    Multiple integer overflows in process_bin_update function in Memcached, which is responsible for processing multiple commands of Memcached binary protocol, can be abused to cause heap overflow and lead to remote code...

    CVSS9.8Published6 Jan 2017
  6. 4.2%

    The try_read_command function in memcached.c in memcached before 1.4.39 allows remote attackers to cause a denial of service (segmentation fault) via a request to add/set a key, which makes a comparison between...

    CVSS7.5Published17 Jul 2017
  7. 3.0%

    In memcached before 1.5.14, a NULL pointer dereference was found in the "lru mode" and "lru temp_ttl" commands.

    CVSS7.5Published29 Apr 2019
  8. 2.6%

    memcached 1.5.16, when UNIX sockets are used, has a stack-based buffer over-read in conn_to_str in memcached.c.

    CVSS7.5Published30 Aug 2019
  9. 2.3%

    memcached version prior to 1.4.37 contains an Integer Overflow vulnerability in items.c:item_free() that can result in data corruption and deadlocks due to items existing in hash table being reused from free list.

    CVSS7.5Published13 Mar 2018
Precursor Intelligence

Running Memcached? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 19 published vulnerabilities listed under the name Memcached, across 80 versions.

None of Memcached's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Memcached. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.