dragonflydb dragonfly Flaw (CVE-2026-104192) Rated CVSS 9.6
A newly published critical vulnerability in dragonflydb dragonfly carries a CVSS score of 9.6. Here is what is affected and how to respond.
Key points
- CVE-2026-104192 affects dragonflydb dragonfly.
- CVSS 9.6 (Critical).
- No exploitation confirmed yet.
dragonflydb dragonfly is affected by CVE-2026-104192, a security flaw that the National Vulnerability Database rates 9.6 out of 10.
At a glance
- CVE
- CVE-2026-104192
- Product
- dragonflydb dragonfly
- CVSS
- 9.6 Critical
- Weakness
- CWE-415
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: Dragonfly is an in-memory data store built for modern application workloads. Prior to 1.40, OpaqueObjLoader::CreateStream in src/server/rdb_load.cc can associate one streamNACK with a consumer group's global PEL and a consumer-local PEL, then free the shared object when a duplicate consumer entry is rejected. Cleanup subsequently frees the same object again. In the default configuration, where Dragonfly ships with authentication disabled, an unauthenticated client can trigger the double-free by sending a crafted serialized stream to RESTORE, causing allocator corruption, denial of service, and potentially attacker-controlled code execution as the Dragonfly service account. The source fix has not yet been mapped to a published release.
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Dragonflydb | dragonfly | < 1.40 |
CVSS vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H.
Is it being exploited?
There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.
What should you do?
- Identify whether the affected product and versions run in your environment.
- Apply the vendor update listed in the advisory as soon as it is available.
- Limit network exposure of the affected service until it is patched.
- Monitor the vendor advisory for updated guidance or exploitation reports.
What to do and how to stay safe: CVE-2026-104192
- Patch scores alone ignore context like network exposure and asset criticality.
- You must map vulnerabilities to specific business risks to prioritize correctly.
- Continuous exposure data replaces static scanning for accurate prioritization.
Prioritize vulnerabilities by actual exploitability and business impact, not by theoretical severity scores. Update your asset context and exposure data continuously to maintain accurate risk rankings.
Step-by-step guide: Risk Based Vulnerability Management: Prioritize Fixes by Actual Threat
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-104192?
CVE-2026-104192 is a CWE-415 vulnerability in dragonflydb dragonfly.
How severe is CVE-2026-104192?
It has a CVSS score of 9.6 Critical.
Is CVE-2026-104192 being exploited?
There is no public confirmation of exploitation at the time of publication.
