# CVE-2026-47784: Information disclosure in memcached

> An attacker can exploit a timing side channel in SASL authentication to potentially recover password data from memcached.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 May 2026
- **Updated:** 20 May 2026
- **Also known as:** AZL-87005, BIT-memcached-2026-47784, DEBIAN-CVE-2026-47784, GHSA-r4h3-4q3v-2776, MINI-56gj-c53w-xq59, MINI-cjxc-jwc7-rpvg, RHSA-2026:23261, UBUNTU-CVE-2026-47784

## What is CVE-2026-47784?

CVE-2026-47784 is a high-severity vulnerability in memcached, published on 20 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In memcached before 1.6.42, password data for SASL password database authentication has a timing side channel because memcmp is used by sasl_server_userdb_checkpass.

Weakness: CWE-208 (Observable Timing Discrepancy)

## Which versions are affected by CVE-2026-47784?

1 open source package ship an affected version, including memcached. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `memcached` | Bitnami | All versions | 1.6.42 |
| `memcached` | Red Hat:hummingbird:1 | All versions | 0:1.6.42-0.1.hum1 |
| `memcached-devel` | Red Hat:hummingbird:1 | All versions | 0:1.6.42-0.1.hum1 |
| `memcached-selinux` | Red Hat:hummingbird:1 | All versions | 0:1.6.42-0.1.hum1 |

Products: Memcached Memcached.

## How do I fix CVE-2026-47784?

Upgrade memcached to 1.6.42 or later.

## Is CVE-2026-47784 being exploited?

There is no known exploitation of CVE-2026-47784 in the wild and no public exploit code.

## Other vulnerabilities in memcached

- [CVE-2023-46853](https://insights.sbomify.com/CVE-2023-46853/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-8704](https://insights.sbomify.com/CVE-2016-8704/): Integer overflow in Memcached (critical 9.8)
- [CVE-2016-8705](https://insights.sbomify.com/CVE-2016-8705/): Integer overflow in Memcached (critical 9.8)
- [CVE-2026-47783](https://insights.sbomify.com/CVE-2026-47783/): Information disclosure in memcached (high 8.1)
- [CVE-2016-8706](https://insights.sbomify.com/CVE-2016-8706/): Integer overflow in Memcached (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47784 and fix it if it is affected.

What it is: CVE-2026-47784 is a high-severity vulnerability in memcached, published on 20 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47784 in the wild and no public exploit code.

Affected packages and fixed versions:
- memcached (Bitnami): affected all versions; fixed in 1.6.42

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47784/ (Markdown: https://insights.sbomify.com/CVE-2026-47784/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47784
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47784
- OSV: https://osv.dev/vulnerability/CVE-2026-47784

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47784/
Summaries are generated and may contain mistakes; the official description above is the record.