Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-44436Published 2026-07-16

CVE-2026-44436 — h2o quicly

high

As of 2026-07-17, CVE-2026-44436 is a HIGH-severity vulnerability in h2o quicly, CVSS v3.1 7.5, EPSS 0.2% (19.8th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-44436 as of 2026-07-17; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
7.5/10High
EPSS
0.2%Higher than 19.8% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
4.5/10Threadlinqs triage score
Published
Updated 2026-07-17
CVSS v3.1 7.5 (HIGH) · EPSS 0.2% (higher than 19.8% of all scored CVEs) · Priority 4.5/10 · Published 2026-07-16

Last updated:

What is CVE-2026-44436?

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.

The record classifies CVE-2026-44436 under weakness classes CWE-120, CWE-787. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 81 days ago.

Severity and exploitation probability

CVSS v3.1 base score
7.5 — HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (FIRST)
0.2% probability of exploitation in the next 30 days, higher than 19.8% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
4.5/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-07-16, last modified 2026-07-17

Is CVE-2026-44436 being exploited?

It currently carries a trending score of 34 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-44436

No vendor patch reference has been recorded for CVE-2026-44436 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-44436

No threat campaign in the Threadlinqs corpus currently references CVE-2026-44436, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, FIRST EPSS. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Other references