CVE-2026-40170: ngtcp2 has a qlog transport parameter serialization stack buffer overflow
ngtcp2 is a C implementation of the IETF QUIC protocol. In versions prior to 1.22.1, ngtcp2_qlog_parameters_set_transport_params() serializes peer transport parameters into a fixed 1024-byte stack buffer without bounds checking. When qlog is enabled, a remote peer can send sufficiently large transport parameters during the QUIC handshake to cause writes beyond the buffer boundary, resulting in a stack buffer overflow. This affects deployments that enable the qlog callback and process untrusted peer transport parameters. This issue has been fixed in version 1.22.1. If developers are unable to immediately upgrade, they can disable the qlog on client.
Security readout for executives and security teams
Plain-English summary
CVE-2026-40170 can let an unauthenticated remote peer crash affected ngtcp2-based QUIC software when qlog logging is enabled. The issue is fixed in ngtcp2 1.22.1. The primary business risk is service disruption, not confirmed data theft or code execution based on the supplied sources.
Executive priority
Treat this as a high-priority availability risk for QUIC-enabled systems using ngtcp2 with qlog enabled. Patch or disable qlog promptly, especially on externally reachable services. No supplied source confirms active exploitation, so urgency should be driven by exposure and service criticality.
Technical view
Before 1.22.1, ngtcp2_qlog_parameters_set_transport_params() writes peer QUIC transport parameters into a fixed 1024-byte stack buffer without bounds checks. With qlog enabled, oversized peer transport parameters during handshake can trigger a stack buffer overflow. CVSS 3.1 is 7.5, network-reachable, unauthenticated, availability impact high.
Likely exposure
Exposure is likely limited to products or services using ngtcp2 versions earlier than 1.22.1 with qlog callbacks enabled while accepting untrusted QUIC peers. Red Hat advisories indicate downstream packaging attention, but the supplied bundle does not enumerate every affected distribution or application.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The described attack surface is remote QUIC handshake processing when qlog is enabled. The documented impact is a stack buffer overflow causing availability loss; do not assume broader impact without vendor evidence.
Researcher notes
The key condition is qlog-enabled serialization of untrusted peer transport parameters. The fixed commit should be reviewed to confirm bounds-safe serialization behavior. Evidence supports CWE-120 and CWE-121 classification, but the bundle does not provide proof of exploitation in the wild.
Mitigation direction
Upgrade ngtcp2 to version 1.22.1 or later.
If immediate upgrade is not possible, disable qlog on client as vendor guidance states.
Review Red Hat advisories for applicable downstream package updates.
Prioritize internet-facing QUIC services that enable qlog or diagnostic callbacks.
Validation and detection
Inventory applications and packages that embed or link ngtcp2.
Confirm deployed ngtcp2 versions are 1.22.1 or later.
Check whether qlog callbacks are enabled in affected services.
Verify applicable Red Hat errata are installed where Red Hat packages are used.
Review service logs for crash patterns during QUIC handshakes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-120: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-120 · source CWE mapping
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.