CVE-2026-44545

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 74% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

June 3, 2026

Last Modified

July 22, 2026

Advisory Details (1)

Auto-updated Jun 15, 2026
No patch confirmed yet.
generic

daphne/CHANGELOG.txt at main · django/daphne · GitHub

https://github.com/django/daphne/blob/main/CHANGELOG.txt

Vendor Advisories for CVE-2026-44545(9)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatansible-automation-platform-27/controller-rhel9:17872202572026-08-24redhat
redhatautomation-controller-0:4.7.16-1.el9ap2026-08-24redhat
redhatansible-automation-platform-26/controller-rhel9:17872440092026-08-24redhat
redhatpython3.12-daphne-0:4.2.2-1.el9ap2026-08-04redhat
redhatansible-automation-platform-26/lightspeed-rhel9:17857753602026-08-04redhat
redhatansible-automation-platform-25/lightspeed-rhel8:17854301742026-08-04redhat
redhatansible-automation-platform-27/lightspeed-rhel9:17853752732026-08-04redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
python-daphne3.0.1-1 ... 4.2.3-1 (9 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python-daphne4.0.0-1 ... 4.2.3-1 (7 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-daphne4.1.2-24.1.2-2+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-daphne4.1.2-2, 4.2.1-1, 4.2.1-24.2.2-0.1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
daphne0.10.0 ... 4.2.1 (62 versions)4.2.2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 192 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 19:31 UTCEPSS rescore
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-14 05:37 UTCEG score recompute
  6. 2026-09-14 05:37 UTCVendor advisory
  7. 2026-09-13 16:47 UTCEPSS rescore
  8. 2026-09-12 23:36 UTCOSV refresh
  9. 2026-09-12 15:01 UTCEPSS rescore
  10. 2026-09-11 14:53 UTCEPSS rescore
  11. 2026-09-11 09:37 UTCEPSS rescore
  12. 2026-09-10 09:34 UTCEPSS rescore
  13. 2026-09-08 22:00 UTCEPSS rescore
  14. 2026-09-07 16:01 UTCEPSS rescore
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-04 05:06 UTCEPSS rescore
  17. 2026-09-02 14:12 UTCEPSS rescore
  18. 2026-09-01 13:54 UTCEPSS rescore
  19. 2026-08-30 19:17 UTCEPSS rescore
  20. 2026-08-30 01:22 UTCEPSS rescore
  21. 2026-08-28 21:41 UTCEPSS rescore
  22. 2026-08-27 14:25 UTCEPSS rescore
  23. 2026-08-26 14:46 UTCEPSS rescore
  24. 2026-08-25 13:49 UTCEPSS rescore
  25. 2026-08-25 03:40 UTCEG score recompute
Show 75 more
  1. 2026-08-25 03:40 UTCVendor advisory
  2. 2026-08-23 13:35 UTCEG score recompute
  3. 2026-08-23 13:35 UTCVendor advisory
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-21 14:43 UTCVendor advisory
  7. 2026-08-20 23:16 UTCEG score recompute
  8. 2026-08-20 23:16 UTCVendor advisory
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-20 10:05 UTCEG score recompute
  11. 2026-08-20 10:05 UTCVendor advisory
  12. 2026-08-19 17:04 UTCEPSS rescore
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 06:43 UTCVendor advisory
  16. 2026-08-16 17:09 UTCEG score recompute
  17. 2026-08-16 17:09 UTCVendor advisory
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 03:59 UTCEG score recompute
  20. 2026-08-16 03:59 UTCVendor advisory
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 14:49 UTCVendor advisory
  23. 2026-08-15 01:33 UTCEG score recompute
  24. 2026-08-15 01:33 UTCVendor advisory
  25. 2026-08-15 01:30 UTCEPSS rescore
  26. 2026-08-14 12:23 UTCVendor advisory
  27. 2026-08-13 23:13 UTCEG score recompute
  28. 2026-08-13 23:13 UTCVendor advisory
  29. 2026-08-13 22:00 UTCEPSS rescore
  30. 2026-08-13 03:25 UTCVendor advisory
  31. 2026-08-12 14:15 UTCEG score recompute
  32. 2026-08-12 14:15 UTCVendor advisory
  33. 2026-08-12 13:51 UTCEPSS rescore
  34. 2026-08-12 01:05 UTCEG score recompute
  35. 2026-08-12 01:05 UTCVendor advisory
  36. 2026-08-11 11:55 UTCEG score recompute
  37. 2026-08-11 11:55 UTCVendor advisory
  38. 2026-08-11 00:00 UTCEPSS rescore
  39. 2026-08-10 22:45 UTCVendor advisory
  40. 2026-08-10 07:01 UTCVendor advisory
  41. 2026-08-09 17:51 UTCEG score recompute
  42. 2026-08-09 17:51 UTCVendor advisory
  43. 2026-08-09 13:46 UTCEPSS rescore
  44. 2026-08-09 04:42 UTCEG score recompute
  45. 2026-08-09 04:42 UTCVendor advisory
  46. 2026-08-08 16:37 UTCEPSS rescore
  47. 2026-08-08 15:32 UTCVendor advisory
  48. 2026-08-08 02:06 UTCEG score recompute
  49. 2026-08-08 02:06 UTCVendor advisory
  50. 2026-08-07 12:56 UTCVendor advisory
  51. 2026-08-06 23:47 UTCEG score recompute
  52. 2026-08-06 23:47 UTCVendor advisory
  53. 2026-08-06 13:46 UTCEPSS rescore
  54. 2026-08-06 09:49 UTCVendor advisory
  55. 2026-08-05 20:34 UTCEG score recompute
  56. 2026-08-05 20:34 UTCVendor advisory
  57. 2026-08-05 19:17 UTCEPSS rescore
  58. 2026-08-04 19:23 UTCEG score recompute
  59. 2026-08-04 15:10 UTCEPSS rescore
  60. 2026-08-04 10:38 UTCEPSS rescore
  61. 2026-08-02 15:26 UTCEG score recompute
  62. 2026-08-02 02:27 UTCEPSS rescore
  63. 2026-08-01 13:06 UTCEG score recompute
  64. 2026-08-01 04:16 UTCEPSS rescore
  65. 2026-07-31 05:32 UTCEG score recompute
  66. 2026-07-30 16:28 UTCEPSS rescore
  67. 2026-07-30 01:30 UTCEPSS rescore
  68. 2026-07-29 10:25 UTCEG score recompute
  69. 2026-07-28 15:36 UTCEPSS rescore
  70. 2026-07-28 03:31 UTCEG score recompute
  71. 2026-07-27 14:13 UTCEPSS rescore
  72. 2026-07-26 22:41 UTCEG score recompute
  73. 2026-07-26 14:54 UTCEPSS rescore
  74. 2026-07-26 14:54 UTCEPSS rescore
  75. 2026-07-25 14:18 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-44545?
CVE-2026-44545 is a high vulnerability published on June 3, 2026. 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…
When was CVE-2026-44545 disclosed?
CVE-2026-44545 was first published in the National Vulnerability Database on June 3, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44545 actively exploited?
CVE-2026-44545 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.9% of all scored CVEs.
What is the CVSS score of CVE-2026-44545?
CVE-2026-44545 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-44545?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44545, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44545

Explore →

Is Your Infrastructure Affected by CVE-2026-44545?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs