CVE-2026-42944
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 · uneditedNLnet Labs Unbound 1.14.0 up to and including version 1.25.0 has a vulnerability that results in heap overflow when encoding multiple NSID and/or DNS Cookie EDNS and/or EDNS Padding options in the reply packet. The relevant options ('nsid', 'answer-cookie', 'pad-responses' (default)) need to be enabled for the vulnerability to be exploited. An adversary who can query Unbound can exploit the vulnerability by attaching multiple NSID and/or DNS Cookie EDNS and/or EDNS Padding options to the query. A flaw in the size calculation of the EDNS field truncates the correct value which allows the encoder to overflow the available space when writing. Those two combined lead to a heap overflow write of Unbound controlled data and eventually a crash. Unbound 1.25.1 contains a patch with a fix to de-duplicate the EDNS options and a fix to prevent truncation of the EDNS field size calculation.
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 · high confidenceUnbound 1.14.0-1.25.0 contains a heap overflow vulnerability in the EDNS option encoding logic. When multiple NSID, DNS Cookie, or EDNS Padding options are present in a query, a flaw in the size calculation truncates the EDNS field size, causing the encoder to write beyond allocated buffer space. This results in heap overflow of Unbound-controlled data, leading to potential crash.
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.14.0, < 1.25.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Unbound is installed and its versionRun `unbound -V` or `unbound-checkconf -v` to obtain the installed version numberAffected if The installed version is between 1.14.0 and 1.25.0 inclusive (versions 1.14.0 <= version < 1.25.1)
-
Identify if NSID option is enabledSearch the Unbound configuration file (commonly /etc/unbound/unbound.conf or /etc/unbound.conf) for the `nsid` directiveAffected if The `nsid` option is present and enabled in the configuration
-
Identify if DNS Cookie option is enabledSearch the Unbound configuration file for the `answer-cookie` directiveAffected if The `answer-cookie` option is present and enabled in the configuration
-
Identify if EDNS Padding option is enabledSearch the Unbound configuration file for the `pad-responses` directiveAffected if The `pad-responses` option is present and enabled in the configuration
The environment is affected if Unbound version is 1.14.0 through 1.25.0 AND at least one of the options (nsid, answer-cookie, or pad-responses) is enabled in the Unbound 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.25.1
Upgrade to Unbound 1.25.1 or later, which contains fixes for EDNS option de-duplication and size calculation. If immediate patching is not feasible, disable the 'nsid', 'answer-cookie', and 'pad-responses' options until the update can be applied.
Unbound 1.25.1
- Identify the current Unbound version installed using 'unbound -V' or checking the package manager
- Upgrade Unbound to version 1.25.1 or later from the official NLnet Labs repository or your distribution's package manager
- After upgrading, verify the new version is running with 'unbound -V'
- If using 'nsid', 'answer-cookie', or 'pad-responses' options, confirm they are functioning correctly after the upgrade
- Restart the Unbound service to ensure the new version is loaded
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42944 — 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-42944 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