Vulnerability in Dragonfly (CVE-2026-47206)
Summary
Vulnerability in Dragonfly (CVE-2026-47206). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.39.9 or later.
Original description
The description as published by the source.
Dragonfly is an in-memory data store built for modern application workloads. Prior to 1.39.9, Dragonfly has a RESP Protocol Injection via Lua redis.error_reply() in EvalSerializer. An authenticated user can inject arbitrary RESP messages into the connection's response stream, potentially causing response desynchronization in connection-pool clients. This vulnerability is fixed in 1.39.9.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47206 has been found in Dragonfly.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Dragonfly to 1.39.9 or later.
If unsure, ask your IT team or search "Dragonfly CVE-2026-47206" on the vendor's site.
CVE-2026-47206 (Dragonfly) — CWE-116
Patched: 1.39.9 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-116) exists in Dragonfly.
Check the vendor advisory for the affected versions of Dragonfly.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.39.9.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Dragonfly' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Dragonfly' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Dragonflyを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Dragonfly to 1.39.9ステージング環境で 1.39.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。