CVE-2026-44436

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (40th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
7.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Quicly is an IETF QUIC protocol implementation intended primarily for use within the H2O HTTP server. Prior to commit 8b178e6, Quicly is vulnerable to a Denial of Service attack through connection state corruption. In QUIC Invariants, the maximum length of a Connection ID is 255 bytes, while QUIC version 1 further restricts the maximum to 20 bytes. Quicly implements QUIC version 1 and therefore its CID buffers are limited to 20 bytes. However, to be able to respond to unknown versions of QUIC, its packet decoder accepts Connection IDs of up to 255 bytes. As its CID buffers are merely 20 bytes long, Quicly must reject QUIC version 1 packets with Connection IDs longer than that. The command line tool bundled with Quicly has had that check, however the library itself lacked such enforcement. As a consequence, when used by applications that lack their own enforcement, the connection state becoming inconsistent to buffer overrun. Fortunately, the overflow stops within the allocated chunk of memory, but nevertheless, the bug leads to assertion failures. This issue has been fixed by commit 8b178e6.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 16, 2026

Last Modified

July 21, 2026

Advisory Details (1)

Auto-updated Jul 16, 2026
Fix referenced — no release confirmed yet. Sources: github.
GitHub advisoryMentions a patch (unverified)

connection state corruption · Advisory · h2o/quicly · GitHub

https://github.com/h2o/quicly/security/advisories/GHSA-v55w-59qx-2v78

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 30× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 131 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 31 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-44436?
CVE-2026-44436 is a high-severity vulnerability; its CVE record was published on July 16, 2026. Quicly is an IETF QUIC protocol implementation intended primarily for use within the H2O HTTP server. Prior to commit 8b178e6, Quicly is vulnerable to a Denial of Service attack through connection state corruption. In QUIC Invariants, the maximum length of a Connection ID is 255 bytes, while QUIC…
When was the CVE record for CVE-2026-44436 published?
The CVE record for CVE-2026-44436 was published on July 16, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 21, 2026; the record at its source may have been updated since.
Is CVE-2026-44436 actively exploited?
CVE-2026-44436 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44436?
CVE-2026-44436 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-44436?
A fix for CVE-2026-44436 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-44436

Explore →

Is Your Infrastructure Affected by CVE-2026-44436?

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

Book a Demo →Browse All CVEs