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 65% 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.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

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.5(medium)
EG Risk
—
EPSS
35.4%
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.
github Patch Available🟡 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

Vendor Advisories for CVE-2026-42304(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntutwisted-doc (25.5.0-5ubuntu0.1) @ resolute2026-06-29ubuntu

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

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
twisted1.0.1 ... 9.0.0 (110 versions)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 8× in last 7d / 39× 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 120 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 in the National Vulnerability Database 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 35.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42304, 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-42304

Explore →

Is Your Infrastructure Affected by CVE-2026-42304?

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

Start Free Scan →Browse All CVEs