Is CVE-2026-44546 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-44546 being exploited in the wild.

How severe is CVE-2026-44546?

Low severity, with a CVSS score of 3.7, published 3 June 2026.

Which products and versions are affected?

Django Software Foundation Daphne < 4.2.2; daphne (PyPI) ECOSYSTEM:introduced=0,fixed=4.2.2.

Is there a fix for CVE-2026-44546?

Yes. daphne (PyPI): upgrade to 4.2.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-44546 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-44546?

Check whether you run Django Software Foundation Daphne or daphne (PyPI) 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.

CVE-2026-44546: Django Daphne header injection in WebSocket handshake

Q: Is there a fix for CVE-2026-44546?

Yes. daphne (PyPI): upgrade to 4.2.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-44546 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-44546?

Check whether you run Django Software Foundation Daphne or daphne (PyPI) 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.

CVE-2026-44546 · Severity: low · CVSS 3.7 · Published 2026-06-03

Daphne, a popular web server for Django applications, is vulnerable to a header smuggling flaw during WebSocket handshakes. An attacker can use non-standard characters to trick the server into processing hidden headers, potentially bypassing security controls or accessing unauthorized data. This issue affects how the server communicates with the application, but it requires specific conditions to exploit and has been fixed in the latest version.

Vendors: Django Software Foundation, PyPI.

Quick answers

Is CVE-2026-44546 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-44546 being exploited in the wild.
How severe is CVE-2026-44546?: Low severity, with a CVSS score of 3.7, published 3 June 2026.
Which products and versions are affected?: Django Software Foundation Daphne < 4.2.2; daphne (PyPI) ECOSYSTEM:introduced=0,fixed=4.2.2.
Is there a fix for CVE-2026-44546?: Yes. daphne (PyPI): upgrade to 4.2.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44546 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-44546?: Check whether you run Django Software Foundation Daphne or daphne (PyPI) 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.

How to fix

daphne (PyPI): upgrade to 4.2.2 or later
```
pip install "daphne>=4.2.2"
```

Technical details

Daphne (before version 4.2.2) reconstructs raw HTTP requests from Twisted's parsed headers and passes them to the Autobahn library for WebSocket handshake processing. A parser differential exists because Twisted does not recognize certain non-standard bytes (such as \x0b, \x0c, \x1c, \x1d, \x1e, or \x85) as line separators, whereas Autobahn's splitlines() method does. An unauthenticated remote attacker can use these characters to smuggle additional headers into the ASGI scope passed to the application. The vulnerability is classified as CWE-444 (HTTP Request/Response Smuggling) and has been addressed in version 4.2.2 by rejecting requests containing these bytes in header values.

Affected products

Django Software Foundation daphne < 4.2.2

Identifiers

CVE-2026-44546
GHSA-xh68-hfp5-5x5m
PYSEC-2026-214

Timeline

2026-06-03: advisory
2026-06-03: disclosed
2026-06-03: patched: Version 4.2.2 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.