CVE-2025-26268
Dragonflydb Dragonfly ≤ 1.27.0
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:LSummary
CVE-2025-26268 is a low-severity Missing Report of Error Condition (CWE-392) vulnerability in Dragonflydb Dragonfly. Its CVSS base score is 3.3 (Low).
Operationally, ranked at the 31th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-14851
Vulnerability Data
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.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Mandates alerting on audit failures, directly providing the missing report of the error condition.
Reporting the security and privacy status to organizational officials ensures monitoring and assessment results are communicated rather than omitted.
Requires reporting and escalation of error conditions and incidents per documented procedures.
IR testing would expose missing error reporting that prevents timely incident detection and response.
Offers direct support for reporting incidents, addressing the failure to report error conditions or security events.
Includes explicit reporting of security status and analysis results, addressing missing reports of error or monitoring conditions.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Requiring log generation directly forces error conditions to be reported so they become visible to monitoring.
Secure SDLC practices include explicit coding standards for reporting all error conditions.
Runtime monitoring can surface unreported errors only if the underlying code already emits them.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can identify missing error reporting through negative test cases and exception handling checks.
Logging of errors and exceptions helps ensure that error conditions are captured and reported.
Monitoring activities can detect missing error reporting by observing abnormal system behavior.
Secure development lifecycle practices include requirements for proper error handling and status reporting.
Application security requirements typically mandate explicit error condition reporting to calling components.
Secure coding standards require functions to return appropriate error codes or status values.