Quick answers
- Is CVE-2026-47206 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47206 being exploited in the wild.
- How severe is CVE-2026-47206?
- Informational severity, with a CVSS score of 2.3, published 26 June 2026.
- Which products and versions are affected?
- DragonflyDB Dragonfly < 1.39.9.
- Is there a fix for CVE-2026-47206?
- A patch was published on 2026-05-18: Fix merged into main branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-47206 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-47206?
- Check whether you run DragonflyDB Dragonfly at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A RESP Protocol Injection vulnerability exists in Dragonfly's EvalSerializer component. The root cause is the failure of `EvalSerializer::OnError()` and `OnStatus()` to sanitize carriage return and line feed (\r\n) sequences in strings returned by Lua's `redis.error_reply()` and `redis.status_reply()` functions. Because RESP uses CRLF as a frame delimiter, an authenticated attacker can inject arbitrary RESP messages into the response stream. This can lead to response desynchronization, where a client using a connection pool misinterprets an injected message as the response to a subsequent, unrelated command. The issue is fixed in version 1.39.9 by stripping CRLF characters from Lua-controlled strings before they are sent to the reply builder.
Affected products
- DragonflyDB Dragonfly < 1.39.9
Timeline
- 2026-05-18: disclosed: Issue reported on GitHub
- 2026-05-18: patched: Fix merged into main branch
- 2026-06-26: advisory: CVE published