NLnet Labs Unbound up to 1.25.0 algorithmic complexity

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.2$0-$5k0.00

Summaryinfo

A vulnerability was found in NLnet Labs Unbound up to 1.25.0. It has been classified as problematic. This affects an unknown function. Performing a manipulation results in algorithmic complexity. This vulnerability is known as CVE-2026-44390. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as problematic, was found in NLnet Labs Unbound up to 1.25.0. This affects an unknown code block. The manipulation with an unknown input leads to a algorithmic complexity vulnerability. CWE is classifying the issue as CWE-407. An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached. This is going to have an impact on availability. The summary by CVE is:

NLnet Labs Unbound up to and including version 1.25.0 has a vulnerability when handling replies with very large RRsets that Unbound needs to perform name compression for. Malicious upstream responses with very large RRsets with records that don't share a suffix above the root can cause Unbound to spend a considerable time applying name compression to downstream replies. This can lead to degraded performance and eventually denial of service in well orchestrated attacks. An adversary can exploit the vulnerability by querying Unbound for the specially crafted contents of a malicious zone with very large RRsets. Before Unbound replies to the query it will try to apply name compression which was an unbounded operation that could lock the CPU until the whole packet was complete. A compression limit was introduced in 1.21.1 for this but it didn't account for the case where records would not share any suffix above the root. That causes Unbound to go in a different code path because of the compression tree lookup failure and eventually not increment the compression counter for those operations. Unbound 1.25.1 contains a patch with a fix that increments the compression counter regardless of the compression tree lookup. This is a complement fix to CVE-2024-8508.

The weakness was published by Qifan Zhang. The advisory is shared at nlnetlabs.nl. This vulnerability is uniquely identified as CVE-2026-44390 since 05/07/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 315778 (Linux Distros Unpatched Vulnerability : CVE-2026-44390), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 1.25.1 eliminates this vulnerability.

The vulnerability is also documented in the databases at Tenable (315778) and CERT Bund (WID-SEC-2026-1599). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Red Hat Enterprise Linux
  • Fedora Linux
  • Ubuntu Linux
  • Open Source Unbound
  • cPanel cPanel/WHM

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.2

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.3
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Algorithmic complexity
CWE: CWE-407 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 315778
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2026-44390

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Unbound 1.25.1

Timelineinfo

05/07/2026 CVE reserved
05/20/2026 +13 days Advisory disclosed
05/20/2026 +0 days VulDB entry created
05/26/2026 +6 days VulDB entry last update

Sourcesinfo

Advisory: nlnetlabs.nl
Researcher: Qifan Zhang
Status: Confirmed

CVE: CVE-2026-44390 (🔒)
GCVE (CVE): GCVE-0-2026-44390
GCVE (VulDB): GCVE-100-364845
CERT Bund: WID-SEC-2026-1599 - Unbound: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Entryinfo

Created: 05/20/2026 12:57
Updated: 05/26/2026 23:04
Changes: 05/20/2026 12:57 (68), 05/21/2026 04:27 (2), 05/23/2026 22:24 (10), 05/26/2026 23:04 (7)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!