Vulnerability in daphne (CVE-2026-44546)
Summary
Vulnerability in daphne (CVE-2026-44546). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.2.2 or later.
Original description
The description as published by the source.
daphne before 4.2.2 reconstructs a raw HTTP request from Twisted's parsed headers and feeds it to autobahn for WebSocket handshake processing. Twisted does not treat \x0b, \x0c, \x1c, \x1d, \x1e, or \x85 as header line separators, but autobahn decodes header values to str and calls splitlines(). An attacker can exploit this parser differential to inject additional headers into the ASGI scope passed to the application. daphne now rejects requests with these bytes in any header value with a 400 response.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-44546 has been found in daphne.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/10.
What to do: upgrade daphne to 4.2.2 or later.
If unsure, ask your IT team or search "daphne CVE-2026-44546" on the vendor's site.
CVE-2026-44546 (daphne) — CWE-444 / CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 4.2.2 — 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-444) exists in daphne.
Check the vendor advisory for the affected versions of daphne.
Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.
Update to 4.2.2.
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 'daphne' . 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 'daphne' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
daphneを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade daphne to 4.2.2ステージング環境で 4.2.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-44546 python-daphne
- Ubuntu UBUNTU-CVE-2026-44546 python-daphne
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com