Skip to main content
VulnerabilityPublished Updated

CVE-2026-101337: Nsd · When base64 data is split up in pieces, of 3 character or less, tokens were incorrectly

Affects nsdSource GCVE Database

0
Authoritative record:CVE-2026-101337· High 8.7

Not known to be exploited · CVSS 8.7 High.

Data as of 28 Oct 2026, 22:30 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Ubuntu 26.10nsdpkg:deb/ubuntu/nsd?arch=source&distro=stonkingOther threatsAffected
  • 4.14.0-1 – 4.15.0-1build1
5 affected builds
Fixed in–
Ubuntu Pro 26.04 LTSnsdpkg:deb/ubuntu/nsd?arch=source&distro=esm-apps/resoluteOther threatsAffected
  • 4.12.0-1 – 4.14.0-1ubuntu0.1~esm1
4 affected builds
Fixed in–
Ubuntu Pro 24.04 LTSnsdpkg:deb/ubuntu/nsd?arch=source&distro=esm-apps/nobleOther threatsAffected
  • 4.7.0-1 – 4.8.0-1ubuntu0.1~esm1
5 affected builds
Fixed in–
Ubuntu Pro 22.04 LTSnsdpkg:deb/ubuntu/nsd?arch=source&distro=esm-apps/jammyOther threatsAffected
  • 4.3.5-1 – 4.3.9-1ubuntu0.1~esm1
6 affected builds
Fixed in–
Ubuntu Pro 20.04 LTSnsdpkg:deb/ubuntu/nsd?arch=source&distro=esm-apps/focalOther threatsAffected
  • =4.1.26-1
  • =4.1.26-1build1
  • =4.1.26-1ubuntu0.1~esm1
Fixed in–
Ubuntu Pro 18.04 LTSnsdpkg:deb/ubuntu/nsd?arch=source&distro=esm-apps/bionicOther threatsAffected
  • 4.1.16-1build1 – 4.1.17-1ubuntu0.1~esm1
4 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

When base64 data is split up in pieces, of 3 character or less, tokens were incorrectly calculated to produce 0 bytes. This enables attackers to overwrite the stack with up to 64K of attacker controlled data. Zone files which are written out by NSD itself, such as for zones for which the NSD instance is secondary, will not be formatted like this. The zone file must be fed to NSD directly, (but it could come, for example, from an operator controlled provisioning system).

References

Community reviews

Loading reviews…