CVE-2026-44545: daphne before 4.2.2 did not pass maxFramePayloadSize or maxMessagePayloadSize to Autobahn's WebSocketServerFac

Q: How do I fix CVE-2026-44545?

daphne: upgrade to 4.2.2. Exact commands for each OS are on this page.

Q: Is CVE-2026-44545 being exploited?

CVE-2026-44545 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-44545 affect?

CVE-2026-44545 affects daphne. Severity is medium (CVSS 5.3). daphne before 4.2.2 did not pass maxFramePayloadSize or maxMessagePayloadSize to Autobahn's WebSocketServerFactory. Because Autobahn defaults both values to 0 (unlimited), an unauthenticated remote attacker could send arbitrarily large WebS

Q: How urgent is CVE-2026-44545?

Priority 30/100. Remotely exploitable, no login, no user action

Routine

MEDIUM 5.3REMOTEUPGRADE

CVE-2026-44545 is a medium-severity flaw (CVSS 5.3) affecting daphne. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

daphne before 4.2.2 did not pass maxFramePayloadSize or maxMessagePayloadSize to Autobahn's WebSocketServerFactory. Because Autobahn defaults both values to 0 (unlimited), an unauthenticated remote attacker could send arbitrarily large WebSocket messages or frames, causing excessive memory consumption and a denial of service.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.3% (top 74%)
CISA exploited list	No
Weakness	CWE-770
Published	2026-06-03
Last modified	2026-07-22

Publisher (CNA): Django Software Foundation · Vendor: djangoproject

Last updated 2026-07-22 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-03 14:16 UTCPublished CVE record published
2026-07-22 19:10 UTCUpdated Record last modified

djangoproject daphne UPGRADE

Affected: < 4.2.2

Fixed in: 4.2.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy daphne || rpm -q daphne || daphne --version

2. UPGRADE to 4.2.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade daphne

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade daphne

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-44545?

daphne: upgrade to 4.2.2. Exact commands for each OS are on this page.

Is CVE-2026-44545 being exploited?

CVE-2026-44545 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-44545 affect?

CVE-2026-44545 affects daphne. Severity is medium (CVSS 5.3). daphne before 4.2.2 did not pass maxFramePayloadSize or maxMessagePayloadSize to Autobahn's WebSocketServerFactory. Because Autobahn defaults both values to 0 (unlimited), an unauthenticated remote attacker could send arbitrarily large WebS

How urgent is CVE-2026-44545?

Priority 30/100. Remotely exploitable, no login, no user action

Related CVEs

CVE-2026-44546 LOW 3.7 UPGRADE daphne before 4.2.2 reconstructs a raw HTTP request from Twisted's parsed headers and feeds it to autobahn for

References

← Back to latest CVEs