CVE-2026-50046 Vulnerability Analysis & Exploit Details

CVE-2026-50046
Vulnerability Scoring

5.9
/10
Significant Risk

Security assessments indicate that CVE-2026-50046 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-50046 Details

Status: Analyzed

Last updated: 🕜 24 Jul 2026, 13:55 UTC
Originally published on: 🕑 22 Jul 2026, 14:17 UTC

Time between publication and last update: 1 days

CVSS Release: version 3

CVSS3 Source

sep@nlnetlabs.nl

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2026-50046 Vulnerability Summary

CVE-2026-50046: In NLnet Labs Unbound 1.15.0 up to and including 1.25.1, the TLS server name used for DNS-over-TLS (DoT) forwarded queries is tied to a struct's ('serviced_query') lifetime but also referenced by another struct ('waiting_tcp'). When the owning struct is jostled out of the mesh while the DoT TCP stream is still handshaking it frees the storage behind the referenced string and if the TLS stream then errors out, it dereferences the freed pointer. The dereference is read-only and the practical impact is a daemon crash resulting in denial of service. A malicious actor that knows a DoT forwarding/stub Unbound's configuration could exploit the vulnerability by quering records in the appropriate zone while keeping Unbound uder pressure so that the jostle logic kicks in. If answers for the vulnerable zone are slow, the likelihood of jostling such queries is higher, although the timing of the jostle needs to be precise. Requirements for a vulnerable Unbound is the existence of a stub/forward zone configured for DoT together with a configured '#authname' suffix on the server identification. The connectivity to the server needs to exhibit a transient failure at the correct time in order to kick off the vulnerable error path.

Assessing the Risk of CVE-2026-50046

Access Complexity Graph

The exploitability of CVE-2026-50046 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-50046

CVE-2026-50046 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-50046, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-50046, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2026-50046 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2026-50046 poses no threat to data integrity.
  • Availability: High
    CVE-2026-50046 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-50046 References

External References

CWE Common Weakness Enumeration

CWE-416

Vulnerable Configurations

  • cpe:2.3:a:nlnetlabs:unbound:1.15.0:-:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.15.0:-:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.15.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.15.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.16.0:-:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.16.0:-:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.16.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.16.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.16.1:*:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.16.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.16.1:-:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.16.1:-:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.16.1:rc1:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.16.1:rc1:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.16.2:*:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.16.2:*:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.16.3:*:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.16.3:*:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.17.0:-:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.17.0:-:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.17.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.17.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.17.1:-:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.17.1:-:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.17.1:rc1:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.17.1:rc1:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.17.1:rc2:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.17.1:rc2:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.18.0:-:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.18.0:-:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.18.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.18.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.19.0:-:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.19.0:-:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.19.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.19.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.19.1:*:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.19.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.19.2:*:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.19.2:*:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.19.3:-:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.19.3:-:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.19.3:rc1:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.19.3:rc1:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.19.3:rc2:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.19.3:rc2:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.20.0:-:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.20.0:-:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.20.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.20.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.21.0:-:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.21.0:-:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.21.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.21.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.21.1:*:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.21.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.22.0:-:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.22.0:-:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.22.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.22.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.23.0:-:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.23.0:-:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.23.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.23.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.23.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.23.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.23.1:*:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.23.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.24.0:-:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.24.0:-:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.24.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.24.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.24.1:*:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.24.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.24.2:*:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.24.2:*:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.25.0:-:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.25.0:-:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.25.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.25.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:nlnetlabs:unbound:1.25.1:*:*:*:*:*:*:*
    cpe:2.3:a:nlnetlabs:unbound:1.25.1:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-50046: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-97663 – The Customer Reviews for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Author Name in all versions up t...
  • CVE-2026-97641 – The Relevanssi – A Better Search plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content in all versions up to, and i...
  • CVE-2026-97637 – The JSON API Auth plugin for WordPress is vulnerable to Authentication Bypass via Cached Session Cookie Disclosure in all versions up to, and inclu...
  • CVE-2026-97634 – The Event Tickets and Registration plugin for WordPress is vulnerable to generic SQL Injection via the 'orderby' parameter in all versions up to, a...
  • CVE-2026-97342 – The JetFormBuilder — Dynamic Blocks Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'choice' Post Meta via Inser...