# CVE-2025-26268: Denial of service in Dragonfly

> Authenticated users can crash the DragonflyDB daemon by sending a crafted Redis command with an invalid scan cursor.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Apr 2025
- **Updated:** 17 Apr 2025
- **Also known as:** GHSA-w33v-rv28-x6m6

## What is CVE-2025-26268?

CVE-2025-26268 is a low-severity denial of service vulnerability in DragonflyDB Dragonfly, published on 17 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

DragonflyDB Dragonfly before 1.27.0 allows authenticated users to cause a denial of service (daemon crash) via a crafted Redis command. The validity of the scan cursor was not checked.

Weakness: CWE-392 (Missing Report of Error Condition)

## Which versions are affected by CVE-2025-26268?

It affects 1 product.


Products: Dragonflydb Dragonfly.

## How do I fix CVE-2025-26268?

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

## Is CVE-2025-26268 being exploited?

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

## Other vulnerabilities in DragonflyDB Dragonfly

- [CVE-2025-26269](https://insights.sbomify.com/CVE-2025-26269/): Integer overflow in Dragonfly (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-26268 and fix it if it is affected.

What it is: CVE-2025-26268 is a low-severity denial of service vulnerability in DragonflyDB Dragonfly, published on 17 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-26268 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-2025-26268/ (Markdown: https://insights.sbomify.com/CVE-2025-26268/index.md)
```

## Sources

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

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