Description
When ranges are used for access control (i.e. of the form 1.2.3.4-1.2.3.25), because NSD wrongly compares the IP address with the range on little endian systems, IPs that were meant to be allowed may be denied, and, IPs that were meant to be denied access could be allowed. An IPv4 address is compared with IPv4 ranges as unsigned 32 bit numbers directly with the endianness of the host, but the values to compare are in network byte order (big-endian). With IPv6 addresses the comparison is done in 4 times a unsigned 32 bit number comparison, again with the endianness of the host where all values are actually in network bye order.
Published: 2026-08-26
Score: 8.2 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

NSD incorrectly compares IPv4 and IPv6 addresses against ACL ranges on little endian systems by using the host’s byte order instead of network byte order. This logic fault causes IP addresses that should be allowed to be denied and IP addresses that should be denied to be allowed, creating a risk of unauthorized access or service disruption. The flaw is categorized as an access‑control weakness (CWE‑284) and a logic error (CWE‑697).

Affected Systems

NLnet Labs NSD versions prior to 4.15.1 are vulnerable. The official fix was released with NSD 4.15.1 and all later releases.

Risk and Exploitability

The CVSS score of 8.2 demonstrates high severity, but the EPSS score is currently unavailable. The vulnerability is not listed in the CISA KEV catalog. Because the flaw operates on IP comparison during normal DNS request handling, it is likely exploitable remotely by passing traffic that falls within or outside the intended ACL ranges. Once the altered comparison is triggered, an attacker could evade ACL restrictions or block legitimate clients, thereby compromising confidentiality, integrity, or availability of the DNS service.

Generated by OpenCVE AI on August 26, 2026 at 09:22 UTC.

Remediation

Vendor Solution

This issue is fixed in 4.15.1 and all later versions.


OpenCVE Recommended Actions

  • Upgrade NSD to version 4.15.1 or later.
  • If an upgrade cannot be performed immediately, modify the NSD configuration to avoid using ACL ranges or replace them with single‑address entries or allowlists that are not impacted by endianness.
  • Maintain monitoring of DNS logs to detect anomalous access patterns that could indicate exploitation of the ACL logic flaw.

Generated by OpenCVE AI on August 26, 2026 at 09:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 26 Aug 2026 08:45:00 +0000

Type Values Removed Values Added
Description When ranges are used for access control (i.e. of the form 1.2.3.4-1.2.3.25), because NSD wrongly compares the IP address with the range on little endian systems, IPs that were meant to be allowed may be denied, and, IPs that were meant to be denied access could be allowed. An IPv4 address is compared with IPv4 ranges as unsigned 32 bit numbers directly with the endianness of the host, but the values to compare are in network byte order (big-endian). With IPv6 addresses the comparison is done in 4 times a unsigned 32 bit number comparison, again with the endianness of the host where all values are actually in network bye order.
Title Wrong interpretation of ACL ranges
Weaknesses CWE-284
CWE-697
References
Metrics cvssV4_0

{'score': 8.2, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: NLnet Labs

Published:

Updated: 2026-08-26T08:37:21.775Z

Reserved: 2026-08-03T13:23:02.012Z

Link: CVE-2026-18664

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-26T09:30:04Z

Weaknesses