# CVE-2026-111279: Dragonfly through 2.0.2 Unbounded Memory Allocation via Negative COUNT in HRANDFIELD, ZRANDMEMBER and SRANDMEMBER

> Unauthenticated attackers can crash the Dragonfly database by sending commands with negative COUNT values, causing memory exhaustion.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-w5x4-fq2q-m366

## What is CVE-2026-111279?

CVE-2026-111279 is a high-severity denial of service vulnerability in dragonflydb dragonfly, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dragonfly through 2.0.2 contains an unbounded memory allocation vulnerability that allows unauthenticated clients to exhaust memory by passing a negative COUNT to HRANDFIELD, ZRANDMEMBER or SRANDMEMBER. Attackers can send a single command against a one-element key with a huge negative COUNT to trigger the OOM killer, terminating the instance for all clients.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value)

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


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

No fix has been published for CVE-2026-111279 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-111279 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111279 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111279 is a high-severity denial of service vulnerability in dragonflydb dragonfly, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111279 exists.

Affected product: dragonflydb dragonfly. 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-2026-111279/ (Markdown: https://insights.sbomify.com/CVE-2026-111279/index.md)
```

## Sources

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

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