A malformed zone may contain an NS or DNAME node above its origin, which named treats as a zone cut. If an attacker inserts a malformed zone into a BIND authoritative server (e.g., via zone transfer), queries for names inside the configured zone then lose authoritative status and return an out-of-zone delegation. On a server that also provides recursion BIND can follow this locally sourced cut and cache attacker-supplied data, affecting names outside the configured zone. This situation persists as long as the malformed zone remains in the zone database.
This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
CVE-2026-78301
Score 5.8 from GitHub Security Advisory published 2026-09-16. a secondary CVSS source baseline 5.8; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.8
- EG Score
- 5.8(high)
- EG Risk
- 26(Track)EG Risk 26/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity58% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 8%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 17, 2026
Advisory Details (3)
Auto-updated Sep 16, 2026CVE-2026-78301: Out-of-zone database nodes can become authoritative zone cuts
https://kb.isc.org/docs/cve-2026-78301Vendor Advisories for CVE-2026-78301(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 18:34 UTCEG score recompute
- 2026-09-18 18:34 UTCGHSA enrichment
- 2026-09-17 19:27 UTCEG score recompute
- 2026-09-17 19:27 UTCGHSA enrichment
- 2026-09-17 18:59 UTCEG score recompute
- 2026-09-17 18:58 UTCGHSA enrichment
- 2026-09-17 18:37 UTCGHSA enrichment
- 2026-09-16 19:32 UTCEG score recompute
- 2026-09-16 19:32 UTCGHSA enrichment
- 2026-09-16 14:23 UTCEG score recompute
- 2026-09-16 14:06 UTCEG score recompute
- 2026-09-16 14:05 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-78301?
When was CVE-2026-78301 disclosed?
Is CVE-2026-78301 actively exploited?
What is the CVSS score of CVE-2026-78301?
How do I remediate CVE-2026-78301?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-78301
Is Your Infrastructure Affected by CVE-2026-78301?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.