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.
CVE-2026-104192
CRITICALPre-NVD 9.69.6
EchelonGraph scoreLOW confidence
This critical-severity CVE scores 9.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). No GitHub Security Advisory CVSS is on record for this CVE.
Triggered by: Headline CVSS from a secondary CVSS source
Sources: a secondary CVSS source
9.6EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 9.6Exploit: None knownExposed services: Not assessed
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
The CVE record's description, written by its CNA (GitHub, Inc.), states the affected versions: "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 entr…" No release containing a fix is confirmed on record.
- CVSS v3
- 9.6
- EG Score
- 9.6CRITICALlow confidence
- EG Risk
- 43EG Risk 43/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity96% × 45%The EG Score, 9.6 of 10.Exploitation0% × 40%No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 13, 2026
Last Modified
October 13, 2026
Advisory Details (3)
Auto-updated Oct 13, 2026🔬 Proof of concept available. No fix on record yet. Sources: github, github_pr, github_commit.
GitHub commit
commit 6c6b27a5cfd0 (dragonflydb/dragonfly)
Fix landed in dragonflydb/dragonfly commit 6c6b27a5cfd0 — awaiting tagged release
https://github.com/dragonflydb/dragonfly/commit/6c6b27a5cfd03d67eb9583ab84a0f0709e3bc77eGitHub pull request
fix(rdb): enforce one-consumer-per-PEL-entry when loading stream groups
Fix merged in dragonflydb/dragonfly PR #7929 on 2026-07-24 — awaiting tagged release
https://github.com/dragonflydb/dragonfly/pull/7929GitHub advisoryMentions a patch (unverified)🟡 PoC Available
DragonflyDB stream RDB deserialization double-free (CWE-415) · Advisory · dragonflydb/dragonfly · GitHub
https://github.com/dragonflydb/dragonfly/security/advisories/GHSA-cg35-6jf4-crfhWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-13 16:26 UTCEG score recompute
- 2026-10-13 15:42 UTCEG score recompute
- 2026-10-13 15:27 UTCEG score recompute
- 2026-10-13 14:50 UTCEG score recomputeFirst assessed: 9.6 CRITICAL
- 2026-10-13 14:49 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-104192?
CVE-2026-104192 is a critical-severity vulnerability; its CVE record was published on October 13, 2026. 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…
When was the CVE record for CVE-2026-104192 published?
The CVE record for CVE-2026-104192 was published on October 13, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 13, 2026; the record at its source may have been updated since.
What is the CVSS score of CVE-2026-104192?
CVE-2026-104192 has a CVSS base score of 9.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-104192?
No fix for CVE-2026-104192 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix. The CVE record's description, written by its CNA (GitHub, Inc.), states the affected versions: "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 entr…" No release containing a fix is confirmed on record.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-104192
Is Your Infrastructure Affected by CVE-2026-104192?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.