BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-44687High confidence

Off-by-one error in 'harden-below-nxdomain' logic can shadow a stub/forward zone by a legitimate parent's NXDOMAIN

NLnet Labs · Unbound

3.7LowCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityLowOperational priority:Low, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.22% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs NLnet Labs Unbound and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

7 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · mainunboundVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.25.2-r0Alpine Security Database ↗Source updated 6 Oct 2026
Alpine v3.22v3.22 · mainunboundVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.25.2-r0Alpine Security Database ↗Source updated 6 Oct 2026
Debian trixietrixie · sourceunboundVendor fix publishedDebian records a fixed source-package version for this release.1.26.1-0+deb13u1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · sourceunboundAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · sourceunboundVendor fix publishedDebian records a fixed source-package version for this release.1.25.2-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · sourceunboundVendor fix publishedDebian records a fixed source-package version for this release.1.25.2-1Debian Security Tracker ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archiveunboundUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-44687 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityunbound: Unbound: Denial of Service due to 'harden-below-nxdomain' logic bypass
20 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • python3-unbound as a component of Red Hat Enterprise Linux 10
  • unbound as a component of Red Hat Enterprise Linux 10
  • unbound-anchor as a component of Red Hat Enterprise Linux 10
  • unbound-devel as a component of Red Hat Enterprise Linux 10
  • unbound-dracut as a component of Red Hat Enterprise Linux 10
  • unbound-libs as a component of Red Hat Enterprise Linux 10
  • unbound-utils as a component of Red Hat Enterprise Linux 10
  • unbound.src as a component of Red Hat Enterprise Linux 10
  • python3-unbound as a component of Red Hat Enterprise Linux 8
  • unbound as a component of Red Hat Enterprise Linux 8
  • unbound-devel as a component of Red Hat Enterprise Linux 8
  • unbound-libs as a component of Red Hat Enterprise Linux 8
Summary
An off-by-one error in Unbound's default harden-below-nxdomain logic can lead to a denial of service. When an intermediate label under a DNSSEC-signed zone is queried, the flaw incorrectly bypasses configured stub or forward zones, disrupting their name resolution.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-47668

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In NLnet Labs Unbound 1.13.2 up to and including 1.25.1, stub or forward zones where the name is below an intermediate labed below a DNSSEC signed zone could be shadowed by the intermediate label's secure NXDOMAIN answer from the parent. This is caused by an off-by-one error in 'harden-below-nxdomain' logic; enabled by default. It effectively bypasses the configuration and the configured stub/forward zone is never contacted. 'harden-below-nxdomain' does an upward DNS cache walk together with a delegation point guard that does not allow NXDOMAIN synthesis above stub/forward zones. The guard tests the domain name but before stripping a label. This results in an iteration where the domain name equals the configured stub/forward zone apex that passes the guard, strips one more label, and probes the cache at the apex's immediate public parent. If that parent has a cached DNSSEC-secure NXDOMAIN, which it will for any private namespace nested two or more labels under a signed public name, the walk returns it and the configured stub/forward upstream is never contacted. This can only be triggered by the query for the intermediate label (between the stub/forward apex and the DNSSEC parent zone).

What

In NLnet Labs Unbound 1.13.2 up to and including 1.25.1, stub or forward zones where the name is below an intermediate labed below a DNSSEC signed zone could be shadowed by the intermediate label's secure NXDOMAIN answer from the parent. This is caused by an off-by-one error in 'harden-below-nxdomain' logic; enabled by default. It effectively bypasses the configuration and the configured stub/forward zone is never contacted. 'harden-below-nxdomain' does an upward DNS cache walk together with a delegation point guard that does not allow NXDOMAIN synthesis above stub/forward zones. The guard tests the domain name but before stripping a label. This results in an iteration where the domain name equals the configured stub/forward zone apex that passes the guard, strips one more label, and probes the cache at the apex's immediate public parent. If that parent has a cached DNSSEC-secure NXDOMAIN, which it will for any private namespace nested two or more labels under a signed public name, the walk returns it and the configured stub/forward upstream is never contacted. This can only be triggered by the query for the intermediate label (between the stub/forward apex and the DNSSEC parent zone).

Why

A product calculates or uses an incorrect maximum or minimum value that is 1 more, or 1 less, than the correct value.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In NLnet Labs Unbound 1.13.2 up to and including 1.25.1, stub or forward zones where the name is below an intermediate labed below a DNSSEC signed zone could be shadowed by the intermediate label's secure NXDOMAIN answer from the parent. This is caused by an off-by-one error in 'harden-below-nxdomain' logic; enabled by default. It effectively bypasses the configuration and the configured stub/forward zone is never contacted. 'harden-below-nxdomain' does an upward DNS cache walk together with a delegation point guard that does not allow NXDOMAIN synthesis above stub/forward zones. The guard tests the domain name but before stripping a label. This results in an iteration where the domain name equals the configured stub/forward zone apex that passes the guard, strips one more label, and probes the cache at the apex's immediate public parent. If that parent has a cached DNSSEC-secure NXDOMAIN, which it will for any private namespace nested two or more labels under a signed public name, the walk returns it and the configured stub/forward upstream is never contacted. This can only be triggered by the query for the intermediate label (between the stub/forward apex and the DNSSEC parent zone).

Why

A product calculates or uses an incorrect maximum or minimum value that is 1 more, or 1 less, than the correct value.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Off-by-one Error → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-193 ↗

CWE-193: Off-by-one Error. A product calculates or uses an incorrect maximum or minimum value that is 1 more, or 1 less, than the correct value.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-193
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-3038Meinberg LANTIME: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Meinberg LANTIME ausnutzen, um beliebigen Code auszuführen, Berechtigungen zu erweitern, Sicherheitsmaßnahmen zu umgehen, sensible Informationen offenzulegen, Daten zu manipulieren oder Denial-of-Service-Zustände herbeizuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-2492Unbound: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Unbound ausnutzen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Daten zu manipulieren, und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260729Security Bulletin 29 Jul 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 29 Jul 2026, published on 29 July 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-025344NLnet Labsのunboundにおける境界条件の判定に関する脆弱性

NLnet LabsのUnboundバージョン1.13.2から1.25.1まで(1.25.1を含む)において、DNSSECで署名されたゾーンの中間ラベルの下に名前が位置するstubまたはforwardゾーンが、親ゾーンからの中間ラベルに対する安全なNXDOMAIN応答によってシャドウイングされる可能性があります。これは、'harden-below-nxdomain'ロジックにおけるオフバイワンのエラーが原因であり、このロジックはデフォルトで有効になっています。結果として、設定が実質的にバイパスされ、設定されたstub/forwardゾーンにはアクセスされなくなります。'harden-below-nxdomain'は、上方向へのDNSキャッシュウォークを行い、stub/forwardゾーンの上でのNXDOMAIN合成を許可しないデリゲーションポイントガードと連動します。このガードはドメイン名をテストしますが、ラベルを取り除く前にテストを行うため、ドメイン名が設定されたstub/forwardゾーンのエイペックスと等しい状態でガードを通過し、さらに1つラベルを剥ぎ取り、エイペックスの直上の公開親キャッシュをプローブします。その親がDNSSECで保護されたNXDOMAINをキャッシュしている場合(これは署名済みの公開名の下に2つ以上のラベルでネストされたプライベート名前空間で発生します)、ウォークはそのNXDOMAINを返し、設定されたstub/forwardゾーンの上流には一切アクセスされません。この問題は、中間ラベル(stub/forwardのエイペックスとDNSSEC親ゾーンの間)へのクエリによってのみ誘発されます。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 22 Jul 2026 · Last source change 22 Jul 2026, 14:19 UTC · CWE-193 · Off-by-one Error

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-47668
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    1.13.2 < 1.25.2 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    1.13.2 < 1.25.2 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    python3-unbound as a component of Red Hat Enterprise Linux 10; unbound as a component of Red Hat Enterprise Linux 10; unbound-anchor as a component of Red Hat Enterprise Linux 10; unbound-devel as a component of Red Hat Enterprise Linux 10; unbound-dracut as a component of Red Hat Enterprise Linux 10; unbound-libs as a component of Red Hat Enterprise Linux 10; unbound-utils as a component of Red Hat Enterprise Linux 10; unbound.src as a component of Red Hat Enterprise Linux 10; python3-unbound as a component of Red Hat Enterprise Linux 8; unbound as a component of Red Hat Enterprise Linux 8; unbound-devel as a component of Red Hat Enterprise Linux 8; unbound-libs as a component of Red Hat Enterprise Linux 8; unbound.src as a component of Red Hat Enterprise Linux 8; python3-unbound as a component of Red Hat Enterprise Linux 9; unbound as a component of Red Hat Enterprise Linux 9; unbound-devel as a component of Red Hat Enterprise Linux 9; unbound-dracut as a component of Red Hat Enterprise Linux 9; unbound-libs as a component of Red Hat Enterprise Linux 9; unbound.src as a component of Red Hat Enterprise Linux 9; rhcos as a component of Red Hat OpenShift Container Platform 4 · Fixed: unbound-main@aarch64 as a component of Red Hat Hardened Images; unbound-main@noarch as a component of Red Hat Hardened Images; unbound-main@src as a component of Red Hat Hardened Images; unbound-main@x86_64 as a component of Red Hat Hardened Images
    After
    python3-unbound as a component of Red Hat Enterprise Linux 10; unbound as a component of Red Hat Enterprise Linux 10; unbound-anchor as a component of Red Hat Enterprise Linux 10; unbound-devel as a component of Red Hat Enterprise Linux 10; unbound-dracut as a component of Red Hat Enterprise Linux 10; unbound-libs as a component of Red Hat Enterprise Linux 10; unbound-utils as a component of Red Hat Enterprise Linux 10; unbound.src as a component of Red Hat Enterprise Linux 10; python3-unbound as a component of Red Hat Enterprise Linux 8; unbound as a component of Red Hat Enterprise Linux 8; unbound-devel as a component of Red Hat Enterprise Linux 8; unbound-libs as a component of Red Hat Enterprise Linux 8; unbound.src as a component of Red Hat Enterprise Linux 8; python3-unbound as a component of Red Hat Enterprise Linux 9; unbound as a component of Red Hat Enterprise Linux 9; unbound-devel as a component of Red Hat Enterprise Linux 9; unbound-dracut as a component of Red Hat Enterprise Linux 9; unbound-libs as a component of Red Hat Enterprise Linux 9; unbound.src as a component of Red Hat Enterprise Linux 9; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4 · Fixed: unbound-main@aarch64 as a component of Red Hat Hardened Images; unbound-main@noarch as a component of Red Hat Hardened Images; unbound-main@src as a component of Red Hat Hardened Images; unbound-main@x86_64 as a component of Red Hat Hardened Images
    Red Hat Product Security ↗
  4. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-44687 to remediation: access.redhat.com/CVE-2026-44687.
    Before
    remediation: access.redhat.com/CVE-2026-44687
    After
    remediation: access.redhat.com/CVE-2026-44687
    Red Hat Product Security ↗
  5. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    Red Hat Product Security ↗
  6. Affected versionsThe structured affected or fixed version information changed.
    Before
    python3-unbound as a component of Red Hat Enterprise Linux 10; unbound as a component of Red Hat Enterprise Linux 10; unbound-anchor as a component of Red Hat Enterprise Linux 10; unbound-devel as a component of Red Hat Enterprise Linux 10; unbound-dracut as a component of Red Hat Enterprise Linux 10; unbound-libs as a component of Red Hat Enterprise Linux 10; unbound-utils as a component of Red Hat Enterprise Linux 10; unbound.src as a component of Red Hat Enterprise Linux 10; python3-unbound as a component of Red Hat Enterprise Linux 8; unbound as a component of Red Hat Enterprise Linux 8; unbound-devel as a component of Red Hat Enterprise Linux 8; unbound-libs as a component of Red Hat Enterprise Linux 8; unbound.src as a component of Red Hat Enterprise Linux 8; python3-unbound as a component of Red Hat Enterprise Linux 9; unbound as a component of Red Hat Enterprise Linux 9; unbound-devel as a component of Red Hat Enterprise Linux 9; unbound-dracut as a component of Red Hat Enterprise Linux 9; unbound-libs as a component of Red Hat Enterprise Linux 9; unbound.src as a component of Red Hat Enterprise Linux 9; unbound.src as a component of Red Hat Hardened Images; rhcos as a component of Red Hat OpenShift Container Platform 4
    After
    python3-unbound as a component of Red Hat Enterprise Linux 10; unbound as a component of Red Hat Enterprise Linux 10; unbound-anchor as a component of Red Hat Enterprise Linux 10; unbound-devel as a component of Red Hat Enterprise Linux 10; unbound-dracut as a component of Red Hat Enterprise Linux 10; unbound-libs as a component of Red Hat Enterprise Linux 10; unbound-utils as a component of Red Hat Enterprise Linux 10; unbound.src as a component of Red Hat Enterprise Linux 10; python3-unbound as a component of Red Hat Enterprise Linux 8; unbound as a component of Red Hat Enterprise Linux 8; unbound-devel as a component of Red Hat Enterprise Linux 8; unbound-libs as a component of Red Hat Enterprise Linux 8; unbound.src as a component of Red Hat Enterprise Linux 8; python3-unbound as a component of Red Hat Enterprise Linux 9; unbound as a component of Red Hat Enterprise Linux 9; unbound-devel as a component of Red Hat Enterprise Linux 9; unbound-dracut as a component of Red Hat Enterprise Linux 9; unbound-libs as a component of Red Hat Enterprise Linux 9; unbound.src as a component of Red Hat Enterprise Linux 9; rhcos as a component of Red Hat OpenShift Container Platform 4 · Fixed: unbound-main@aarch64 as a component of Red Hat Hardened Images; unbound-main@noarch as a component of Red Hat Hardened Images; unbound-main@src as a component of Red Hat Hardened Images; unbound-main@x86_64 as a component of Red Hat Hardened Images
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-44687 · cve.blacktree.nl