CVE-2026-44434: Quicly is an IETF QUIC protocol implementation intended primarily for use within the H2O HTTP server

Q: How do I fix CVE-2026-44434?

quicly: upgrade to 2026-05-29. Exact commands for each OS are on this page.

Q: Is CVE-2026-44434 being exploited?

CVE-2026-44434 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-44434 affect?

CVE-2026-44434 affects quicly. Severity is medium (CVSS 5.3). Quicly is an IETF QUIC protocol implementation intended primarily for use within the H2O HTTP server. Prior to commit dccf5d4, Quicly was vulnerable to stateless reset injection through lack of packet entry validation. The QUIC protocol is

Q: How urgent is CVE-2026-44434?

Priority 26/100. Remotely exploitable, no login, no user action

Routine

MEDIUM 5.3REMOTEUPGRADE

CVE-2026-44434 is a medium-severity flaw (CVSS 5.3) affecting quicly. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Quicly is an IETF QUIC protocol implementation intended primarily for use within the H2O HTTP server. Prior to commit dccf5d4, Quicly was vulnerable to stateless reset injection through lack of packet entry validation. The QUIC protocol is designed to withstand packet injection attacks, once the handshake is complete. Only packets that carry some secret patterns are considered as stateless resets. Quicly allows the peer to share up to 4 such patt

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.2% (top 89%)
CISA exploited list	No
Weakness	CWE-345, CWE-665
Published	2026-07-16
Last modified	2026-10-24

Publisher (CNA): GitHub, Inc. · Vendor: h2o

Last updated 2026-10-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-07-16 23:16 UTCPublished CVE record published
2026-10-24 20:10 UTCUpdated Record last modified

h2o quicly UPGRADE

Affected: < 2026-05-29

Fixed in: 2026-05-29

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy quicly || rpm -q quicly || quicly --version

2. UPGRADE to 2026-05-29 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade quicly

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade quicly

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-44434?

quicly: upgrade to 2026-05-29. Exact commands for each OS are on this page.

Is CVE-2026-44434 being exploited?

CVE-2026-44434 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-44434 affect?

CVE-2026-44434 affects quicly. Severity is medium (CVSS 5.3). Quicly is an IETF QUIC protocol implementation intended primarily for use within the H2O HTTP server. Prior to commit dccf5d4, Quicly was vulnerable to stateless reset injection through lack of packet entry validation. The QUIC protocol is

How urgent is CVE-2026-44434?

Priority 26/100. Remotely exploitable, no login, no user action

Related CVEs

CVE-2026-44435 HIGH 7.5 UPGRADE Quicly is an IETF QUIC protocol implementation intended primarily for use within the H2O HTTP server
CVE-2026-44436 HIGH 7.5 UPGRADE Quicly is an IETF QUIC protocol implementation intended primarily for use within the H2O HTTP server
CVE-2026-44433 MEDIUM 5.3 UPGRADE Quicly is an IETF QUIC protocol implementation intended primarily for use within the H2O HTTP server

References

← Back to latest CVEs