Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
MEDIUM severity

GHSA-rrc9-mx66-ffcm — daphne

MEDIUM

GHSA-rrc9-mx66-ffcm is a medium-severity (CVSS 5.3) CWE-770 vulnerability in daphne. A fix is available for daphne — see the affected versions and patch details below.

daphne: Unauthenticated attackers can cause excessive memory consumption by sending arbitrarily large WebSocket messages/frames

Also known asCVE-2026-44545PYSEC-2026-213
Published
Jun 3, 2026
Updated
Jul 11, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 25, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-rrc9-mx66-ffcm.

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs45th percentile — riskier than 45% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-rrc9-mx66-ffcm plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected
🐍daphne

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIdaphneall versions4.2.2pip install --upgrade 'daphne==4.2.2'

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for daphne, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update daphne to 4.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rrc9-mx66-ffcm is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rrc9-mx66-ffcm can be triaged on real exposure rather than presence alone.

Tailored to GHSA-rrc9-mx66-ffcm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant
ProductFixed inAdvisory
Red Hat Ansible Automation Platform 2.5 for RHEL 8python3.12-daphne-0:4.2.2-1.el8apRHSA-2026:50319
Red Hat Ansible Automation Platform 2.6 for RHEL 9python3.12-daphne-0:4.2.2-1.el9apRHSA-2026:50336
Red Hat Ansible Automation Platform 2.6 for RHEL 9automation-controller-0:4.7.16-1.el9apRHSA-2026:59136
Red Hat Ansible Automation Platform 2.5ansible-automation-platform-25/lightspeed-rhel8:1785430174RHSA-2026:50357
Red Hat Ansible Automation Platform 2.6ansible-automation-platform-26/eda-controller-rhel9:1785633038RHSA-2026:50479
Red Hat Ansible Automation Platform 2.6ansible-automation-platform-26/controller-rhel9:1787244009RHSA-2026:59155
Red Hat Ansible Automation Platform 2.7ansible-automation-platform-27/eda-controller-rhel9:1785374869RHSA-2026:50340
Red Hat Ansible Automation Platform 2.7ansible-automation-platform-27/controller-rhel9:1787220257RHSA-2026:59153

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-rrc9-mx66-ffcm in your dependencies?

O3 Security finds GHSA-rrc9-mx66-ffcm across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-rrc9-mx66-ffcm: daphne (Medium 5.3) | O3 Security