Skip to main content
Mallory
← Back to News
proof-of-concept-releaseinternet-facing-service-vulnerabilitywidely-deployed-product-advisoryrapid-weaponization

Knot Resolver DNS-over-QUIC Heap Overflow Enables Unauthenticated RCE

Patch & Detection Intelligence · 3 sources · Updated 4mo ago · First seen Jun 8, 2026

Knot Resolver DNS-over-QUIC Heap Overflow Enables Unauthenticated RCE

A remotely triggerable heap buffer overflow in Knot Resolver 6.3.0 allows unauthenticated remote code execution through the kresd DNS-over-QUIC listener. The flaw stems from incorrect size tracking during inbound QUIC STREAM frame reassembly, causing a later memcpy() to write past an allocated heap buffer. Public reporting said a single QUIC connection carrying six crafted STREAM frames can produce a controlled out-of-bounds write and, with heap grooming, overwrite a libgnutls cleanup handler to seize control of a function pointer and argument. Researchers classified the issue as CWE-787 and demonstrated end-to-end RCE in a Debian 12 lab environment with ASLR disabled; failed attempts can also crash worker processes and cause denial of service.

CZ.NIC fixed the vulnerability in Knot Resolver 6.4.1, and full technical details plus working proof-of-concept exploit code were disclosed publicly shortly after the patch release. No in-the-wild exploitation has been confirmed, but the exposure is significant because Knot Resolver is deployed by major ISPs and handles untrusted network traffic, raising the risk of resolver compromise and forged DNS responses for downstream users. Organizations are being urged to upgrade to 6.4.1 immediately; if patching cannot be completed at once, defenders should disable DNS-over-QUIC, restrict access to the DoQ service, and monitor for repeated kresd worker crashes that could indicate exploitation attempts.

Patch this, or something else?See real exploitation activity before you spend the cycle.
Triage this advisory
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

4 events · Jun 8, 2026 – Jul 22, 2026
  1. Jul 22, 20264mo ago

    CZ.NIC releases Knot Resolver 6.4.1 with DoQ overflow fix

    CZ.NIC released Knot Resolver 6.4.1 to fix the remotely triggerable DNS-over-QUIC heap out-of-bounds write in version 6.3.0. The coordinated disclosure write-up identifies 2026-07-22 as the fix release date.

    GitHub - venglin/knot-doq: PoC for a Knot Resolver 6.3.0 DNS-over-QUIC heap overflow (RCE as knot-resolver), fixed in 6.4.1. Coordinated disclosure. · GitHub
  2. Jun 8, 20265mo ago

    Full technical details and working PoC exploit are publicly disclosed

    A researcher publicly released full technical details and working proof-of-concept exploit code for the Knot Resolver DNS-over-QUIC vulnerability. The write-up described how crafted QUIC STREAM frames could achieve end-to-end RCE in a lab environment.

    oss-sec: Knot Resolver 6.3.0 DNS-over-QUIC heap buffer overflow (RCE)
  3. Jun 8, 20265mo ago

    CZ.NIC releases Knot Resolver 6.4.1 with fix

    CZ.NIC fixed the DNS-over-QUIC heap out-of-bounds write in Knot Resolver by releasing version 6.4.1. The vulnerable version identified in the references is Knot Resolver 6.3.0.

    oss-sec: Knot Resolver 6.3.0 DNS-over-QUIC heap buffer overflow (RCE)
  4. Jun 8, 20265mo ago

    Researcher reports Knot Resolver DoQ heap overflow to CZ.NIC

    A remotely triggerable heap buffer overflow in Knot Resolver 6.3.0's DNS-over-QUIC receive path was reported to CZ.NIC. The flaw could lead to unauthenticated remote code execution or, at minimum, worker-process crashes causing denial of service.

    oss-sec: Knot Resolver 6.3.0 DNS-over-QUIC heap buffer overflow (RCE)
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

1 linked
Knot Resolver
Do you run this?See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
Prioritize This Patch
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.