dbcve.org
DnsdistApplication · Powerdns

CVE-2026-24030

HIGH · 7.5 CVSS v3.1 Published 2026-03-31
Fix available
A fix is available. Upgrade to 1.9.12 / 2.0.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An attacker might be able to trick DNSdist into allocating too much memory while processing DNS over QUIC or DNS over HTTP/3 payloads, resulting in a denial of service. In setups with a large quantity of memory available this usually results in an exception and the QUIC connection is properly closed, but in some cases the system might enter an out-of-memory state instead and terminate the process.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

DNSdist versions processing DNS over QUIC (DoQ) or DNS over HTTP/3 (DoH3) lack proper memory allocation bounds when handling incoming payloads, allowing an attacker to trigger excessive memory allocation that can cause denial of service through out-of-memory conditions.

MitigationImplement memory limits and bounds checking on DoQ/DoH3 packet processing, configure appropriate memory thresholds, and consider connection-level rate limiting for QUIC/HTTP/3 endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DnsdistApplication
Affected:>= 1.9.0, < 1.9.12>= 2.0.0, < 2.0.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify dnsdist installation and version
    Run 'dnsdist --version' or check the package manager (e.g., 'rpm -q dnsdist' or 'dpkg -l dnsdist') to determine the installed version
    Affected if The installed version is >= 1.9.0 and < 1.9.12, or >= 2.0.0 and < 2.0.3
  2. Verify DNS over QUIC (DoQ) is enabled
    Review dnsdist configuration files (e.g., /etc/dnsdist.conf, /etc/dnsdist/dnsdist.conf) for 'addDOH3' or 'DOH3Server' directives, or check running process with 'dnsdist --list doh3'
    Affected if DNS over HTTP/3 (DoH3) is configured and active on the server
  3. Verify DNS over HTTP/3 (DoH3) is enabled
    Review dnsdist configuration files for 'addDOH3' or 'DOH3Server' directives, or check running configuration with 'dnsdist --list doh3'
    Affected if DNS over QUIC (DoQ) is configured and active on the server

Your environment is affected if dnsdist version falls within the vulnerable ranges AND DNS over QUIC or DNS over HTTP/3 is enabled in the configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.9.12 / 2.0.3 or later
Fixed in 1.9.122.0.3
Interim mitigation

Implement memory limits and bounds checking on DoQ/DoH3 packet processing, configure appropriate memory thresholds, and consider connection-level rate limiting for QUIC/HTTP/3 endpoints.

Recommended fix High confidence

Upgrade to dnsdist 1.9.12 (1.9.x line) or 2.0.3 (2.0.x line) or later

  1. 1. Identify your current dnsdist version by running 'dnsdist --version'
  2. 2. Stop the dnsdist service (e.g., 'systemctl stop dnsdist' or 'service dnsdist stop')
  3. 3. Update your package repository to ensure you have access to the latest packages
  4. 4. Install the updated dnsdist package: On Debian/Ubuntu use 'apt update && apt install dnsdist', On RHEL/CentOS use 'yum update dnsdist'
  5. 5. Verify the installed version is 1.9.12 or later for the 1.9.x line, or 2.0.3 or later for the 2.0.x line by running 'dnsdist --version'
  6. 6. Start the dnsdist service (e.g., 'systemctl start dnsdist' or 'service dnsdist start')
  7. 7. Monitor logs for any errors during startup
Caveat Review the release notes for 1.9.12 and 2.0.3 for any configuration or behavior changes before upgrading, though minor version upgrades typically have minimal breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dnsdist Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24030 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24030 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data