# CVE-2019-15026: Memory corruption in n/a

> A stack-based buffer over-read in memcached allows attackers to cause denial of service or disclose information when UNIX sockets are enabled.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 30 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-15026, DLA-1913-1, GHSA-p49f-7m7m-pmxv, MGASA-2020-0016, OESA-2021-1006, UBUNTU-CVE-2019-15026, USN-4125-1

## What is CVE-2019-15026?

CVE-2019-15026 is a high-severity memory corruption vulnerability in n/a, published on 30 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2019-15026?

It affects 1 product.


Products: Memcached Memcached.

## How do I fix CVE-2019-15026?

Apply the vendor's patch.

## Is CVE-2019-15026 being exploited?

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

## Other vulnerabilities in n/a

- [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-2026-47784](https://insights.sbomify.com/CVE-2026-47784/): Information disclosure in memcached (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-15026 and fix it if it is affected.

What it is: CVE-2019-15026 is a high-severity memory corruption vulnerability in n/a, published on 30 Aug 2019. 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-2019-15026 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2019-15026/ (Markdown: https://insights.sbomify.com/CVE-2019-15026/index.md)
```

## Sources

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

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