Microsoft · Named may terminate unexpectedly when a redirect zone is used with strict QNAME minimization
Affects MicrosoftSource GCVE Database
Not known to be exploited · CVSS 7.5 High.
Data as of 30 Oct 2026, 07:51 UTC
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ISCBIND 9 | Affected
| Fixed in– |
Iscisc/bind9pkg:deb/isc/bind9Other threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, avoid using redirect zones with strict QNAME minimization enabled in the affected version.
Description
A vulnerability exists in Microsoft product version 3.0 where the Named service may terminate unexpectedly when a redirect zone is used with strict QNAME minimization enabled. This issue could cause service disruption due to unexpected termination.