CVE-2026-55991: Remote DNS-over-QUIC (DoQ) flow-control assertion failure in libngtcp2

Published Jul 22, 2026
·
Updated

In NLnet Labs Unbound 1.22.0 up to and including 1.25.1, a remote unauthenticated client can trigger a libngtcp2 assertion (if compiled with assertions on) and terminate the entire Unbound process using a single DNS-over-QUIC (DoQ) connection and one normal DNS query. This is caused by an erroneous error value passed to libngtcp2. When 'ngtcp2connwritevstream()' returns 'NGTCP2ERRSTREAMDATABLOCKED', Unbound continues to call 'ngtcp2ccerrsetapplicationerror()' with a '-1' error value. The 'int' literal '-1' is implicitly converted to the function's 'uint64t errorcode' parameter as '0xFFFFFFFFFFFFFFFF'. The follow-on 'ngtcp2connwriteconnectionclose()' serialises that value as a QUIC variable-length integer; because '2^64-1' exceeds the 62-bit varint ceiling, 'ngtcp2putuvarintlen()' fails 'assert(n < 4611686018427387904ULL)' and the whole resolver process aborts. A remote, unauthenticated DoQ client can trigger this deterministically with a single QUIC connection by advertising 'initialmaxstreamdatabidilocal = 1' in its transport parameters and sending one DoQ query without ever reading the stream.

Other sources

Remote DNS-over-QUIC (DoQ) flow-control assertion failure in libngtcp2

Microsoft

Affected Software

3 affected componentsFixes available
Nlnet Labs Unbound>=1.22.0<=1.25.1
Microsoft azl3 unbound 1.25.1-1<1.25.2-1
1.25.2-1
nlnetlabs Unbound>=1.22.0<1.25.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.25.2-1
  2. Upgrade

    Upgrade NLnet Labs Unbound to a version that resolves this vulnerability.

    Fixed in 1.25.2

Event History

Jul 22, 2026
CVE Published
via MITRE·01:10 PM
Data Sourced
via MITRE·01:10 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·02:17 PM
DescriptionSeverityWeaknessAffected Software
Jul 23, 2026
Data Sourced
via Microsoft·08:05 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:05 AM
Affected Software
Updated
via Microsoft·08:05 AM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-55991?

The severity of CVE-2026-55991 is medium with a score of 5.9.

2

How do I fix CVE-2026-55991?

To fix CVE-2026-55991, update NLnet Labs Unbound to a version beyond 1.25.1.

3

What systems are affected by CVE-2026-55991?

CVE-2026-55991 affects NLnet Labs Unbound versions 1.22.0 through 1.25.1.

4

What kind of attack does CVE-2026-55991 involve?

CVE-2026-55991 involves a remote unauthenticated client that can terminate the Unbound process through a DNS-over-QUIC connection.

5

Is CVE-2026-55991 exploitable from the internet?

Yes, CVE-2026-55991 can be exploited by a remote unauthenticated client over the internet.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203