CVE-2026-33602
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 · uneditedA rogue backend can send a crafted UDP response with a query ID off by one related to the maximum configured value, triggering an out-of-bounds write leading to a denial of service.
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 confidenceA vulnerability in UDP response handling allows a rogue backend to send a crafted UDP packet with a query ID that exceeds the maximum configured value by one, triggering an out-of-bounds memory write that causes denial of service.
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>= 1.9.0, < 1.9.13>= 2.0.0, < 2.0.4CVSS 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
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed dnsdist versionRun 'dnsdist --version' or check the package version with 'dpkg -l pdns-dnsdist' (Debian/Ubuntu) or 'rpm -qi dnsdist' (RHEL/CentOS)Affected if Version is >= 1.9.0 and < 1.9.13, or >= 2.0.0 and < 2.0.4
-
Verify UDP frontend is enabledCheck dnsdist configuration file (typically /etc/dnsdist/dnsdist.conf) for 'setUDP' or 'addLocal' statements that enable UDP listening portsAffected if UDP frontend is enabled and version is in affected range
-
Identify configured backendsReview dnsdist.conf for 'newServer' statements that define backend servers; check for any backend IP addresses or hostnames that may be untrusted or externally accessibleAffected if Backends are configured and version is in affected range (vulnerability is triggered by rogue backend UDP responses)
You are affected if dnsdist version is 1.9.0 through 1.9.12, or 2.0.0 through 2.0.3, and UDP frontend with backend servers is enabled in the configuration.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.9.132.0.4
Implement proper bounds checking on query IDs before array/index access, validate that query IDs fall within the configured maximum range, and limit trust in backends or use authenticated connections.
Upgrade to dnsdist 1.9.13 (for 1.x branch) or 2.0.4 (for 2.x branch)
- 1. Identify the currently installed dnsdist version using 'dnsdist --version' or your package manager
- 2. For dnsdist 1.x branch: upgrade to version 1.9.13 or later
- 3. For dnsdist 2.x branch: upgrade to version 2.0.4 or later
- 4. Obtain the updated package from your Linux distribution's repository or the official dnsdist repository (repo.powerdns.com)
- 5. Install the updated package using your package manager (e.g., apt-get install dnsdist or yum install dnsdist)
- 6. Restart the dnsdist service to load the updated version
- 7. Verify the installation by running 'dnsdist --version' to confirm the patched version is running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33602 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-33602 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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