CVE-2026-42304

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 64% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
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.9%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Twisted is an event-based framework for internet applications, supporting Python 3.6+. Prior to 26.4.0rc2, the twisted.names module is vulnerable to a Denial of Service (DoS) attack via resource exhaustion during DNS name decompression. A remote, unauthenticated attacker can exploit this by sending a crafted TCP DNS packet containing deeply chained compression pointers. This flaw bypasses previous loop-prevention logic, causing the single-threaded Twisted reactor to hang while processing millions of recursive lookups, effectively freezing the server. This vulnerability is fixed in 26.4.0rc2.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

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%
Exploitation40% × 40%
Automatability100% × 15%
EPSS PROB
0.9%
EPSS %ILE
60th
KEV
Not listed

Published

May 13, 2026

Last Modified

May 19, 2026

Advisory Details (1)

Auto-updated May 13, 2026
🔬 Proof of concept available. Patch available. Sources: github.
githubMentions a patch (unverified)🟡 PoC Available

Denial of Service (DoS) in twisted.names via Crafted DNS Compression Pointer Chains · Advisory · twisted/twisted · GitHub

https://github.com/twisted/twisted/security/advisories/GHSA-grgv-6hw6-v9g4

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntutwisted-doc (22.1.0-2ubuntu2.7) @ jammy2026-08-23ubuntu

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 rangeFix by version rangeDependents
twisted20.3.0-7 ... 26.4.0-4 (30 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
twisted22.4.0-4 ... 26.4.0-4 (22 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
twisted24.11.0-1 ... 26.4.0-4 (10 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
twisted24.11.0-1 ... 25.5.0-5 (6 versions)
  • every version up to 26.4.0-1: fixed in 26.4.0-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
twisted1.0.1 ... 9.0.0 (110 versions)
  • every version up to 26.4.0rc2: fixed in 26.4.0rc2
  • every version up to 26.4.0: fixed in 26.4.0
—

Weakness Classification(2)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 23× 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 228 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-42304?
CVE-2026-42304 is a high vulnerability published on May 13, 2026. Twisted is an event-based framework for internet applications, supporting Python 3.6+. Prior to 26.4.0rc2, the twisted.names module is vulnerable to a Denial of Service (DoS) attack via resource exhaustion during DNS name decompression. A remote, unauthenticated attacker can exploit this by sending…
When was CVE-2026-42304 disclosed?
CVE-2026-42304 was first published on May 13, 2026, with the most recent update on May 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42304 actively exploited?
CVE-2026-42304 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (60th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-42304?
CVE-2026-42304 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-42304?
A fix for CVE-2026-42304 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-42304 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-42304?

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