CVE-2026-62357

Received Received - Intake

Heap Buffer Overflow in Dragonfly CMS.INITBYDIM

Publication date: 2026-08-18

Last updated on: 2026-08-19

Assigner: GitHub, Inc.

Description

Dragonfly is an in-memory data store built for modern application workloads. Prior to 1.40.0, CMS.INITBYDIM and CMS.INITBYPROB accept dimensions whose width times depth times sizeof(int64_t) overflows in src/core/cms.cc, allocating an undersized counter buffer while CMS.INCRBY and CMS.QUERY use the unbounded dimensions, which allows an unauthenticated remote client to corrupt or disclose adjacent heap memory and crash the server. This issue is fixed in version 1.40.0.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-18

Last Modified

2026-08-19

Generated

2026-09-07

AI Q&A

2026-08-18

EPSS Evaluated

2026-09-06

NVD

CVE-2026-62357

EUVD

EUVD-2026-60960

Affected Vendors & Products

Vendor	Product	Version / Range
dragonfly	dragonfly	1.40.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-190	The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

Attack-Flow Graph

Executive Summary

This vulnerability affects Dragonfly, an in-memory data store. Before version 1.40.0, two commands (CMS.INITBYDIM and CMS.INITBYPROB) could accept dimensions that cause an integer overflow when calculating memory allocation. This leads to an undersized buffer being created. Meanwhile, other commands (CMS.INCRBY and CMS.QUERY) use the original dimensions, allowing an attacker to corrupt or read adjacent heap memory, potentially crashing the server.

Detection Guidance

This vulnerability can be detected by checking the Dragonfly version in use. If the version is below 1.40.0, the system is vulnerable. Commands like 'dragonfly-server --version' or inspecting the running process may help identify the version.

Impact Analysis

An unauthenticated remote attacker could exploit this to corrupt or disclose adjacent heap memory, leading to server crashes or unauthorized data access. This could disrupt services relying on Dragonfly and expose sensitive information stored in memory.

Compliance Impact

This vulnerability could lead to unauthorized data access or corruption, violating confidentiality and integrity requirements in GDPR and HIPAA. Organizations using vulnerable Dragonfly versions may face compliance violations, data breach notifications, and potential fines.

Mitigation Strategies

Upgrade Dragonfly to version 1.40.0 or later immediately to address the vulnerability. Ensure no unauthenticated remote clients can access the server until the upgrade is complete.

Hi! I’m here to help you understand CVE-2026-62357. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70