NLnet Labs Unbound up to and including version 1.25.0 has a vulnerability in the jostle logic that could defeat its purpose and degrade resolution performance. Retransmits of the same query could renew the age of slow running queries and not allow the jostle logic to see them as aged and potential targets for replacement with new queries. An adversary who can query a vulnerable Unbound and who can control a domain name server that replies slowly and/or maliciously to Unbound's queries can exploit the vulnerability and degrade the resolution performance of Unbound. When Unbound's 'num-queries-per-thread' reaches its limit, the jostle logic kicks in. When a new query comes in, half of the available queries that are also slow to resolve are candidates for replacement. The vulnerability then happens because duplicate queries that need resolution would skew the aging result by using the timestamp of the latest duplicate query instead of the original one that started the resolution effort. Cache and local data response performance remains unaffected. Coordinated attacks could raise this to a denial of resolution service. Unbound 1.25.1 contains a patch with a fix to attach an initial, non-updatable start time for incoming queries that allow the jostle logic to work as intended.
Security readout for executives and security teams
Plain-English summary
This flaw can make vulnerable Unbound DNS resolvers spend capacity on slow unresolved lookups instead of replacing them efficiently. If abused at scale, users may see DNS resolution delays or failures for uncached domains. Cached and local answers are reported unaffected.
Executive priority
Treat this as a high-priority availability risk for DNS infrastructure. Prioritize exposed recursive resolvers first, because DNS degradation can affect many dependent services even without data theft or system compromise.
Technical view
Unbound through 1.25.0 mishandles jostle aging when duplicate retransmitted queries update the effective timestamp. Slow queries may avoid replacement after num-queries-per-thread is exhausted. An attacker needs query access to Unbound and control of a slow or malicious authoritative server. Unbound 1.25.1 fixes this with a non-updatable initial start time.
Likely exposure
Internet-facing or broadly reachable recursive Unbound resolvers are the primary concern, especially where untrusted clients can send queries. Internal-only resolvers are lower risk but still exposed if compromised or untrusted network segments can query them.
Exploitation context
The bundle does not report active exploitation, and KEV is false. Exploitation requires both access to query the vulnerable resolver and control of a domain name server that responds slowly or maliciously. Coordinated activity could become denial of resolution service.
Researcher notes
Focus validation on duplicate query handling and jostle candidate aging, not cache correctness. The described failure is availability-only: confidentiality and integrity are not impacted by the CVSS vector. Evidence for affected scope and fix comes mainly from NLnet Labs and CVE metadata.
Mitigation direction
Upgrade NLnet Labs Unbound to 1.25.1 or later.
Apply distribution vendor packages, including relevant Red Hat advisories where applicable.
Restrict recursive resolver access to trusted clients and networks.
Monitor resolver saturation, slow uncached lookups, and query queue pressure.
Check vendor guidance for any environment-specific mitigations.
Validation and detection
Inventory Unbound instances and confirm whether versions are 1.25.0 or earlier.
Confirm recursive query access is limited to intended clients.
Review resolver metrics for num-queries-per-thread exhaustion or unusual slow resolutions.
Verify upgraded systems report Unbound 1.25.1 or patched vendor builds.
Confirm cached and local response paths remain normal after remediation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-440: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-440 · source CWE mapping
Expected Behavior Violation
Expected Behavior Violation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Update of Reference Count represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.