How severe is CVE-2026-19667?

CVE-2026-19667 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2026-19667 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (45th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-19667?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-19667 published?

CVE-2026-19667 was published on 2026-09-16 and last updated on 2026-09-17.

CVE-2026-19667

CVE-2026-19667 is a high-severity vulnerability with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-197.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 1% (45th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-197
Published: 2026-09-16
Last modified: 2026-09-17

Description

If an attacker-controlled authoritative server can produce a negative answer that is exactly 65536 bytes, then a flaw in `named` results in a negative cache entry of 0 bytes. When this entry is subsequently read, `named` aborts. 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.

Frequently asked questions

What is CVE-2026-19667?: If an attacker-controlled authoritative server can produce a negative answer that is exactly 65536 bytes, then a flaw in `named` results in a negative cache entry of 0 bytes. When this entry is subsequently read, `named` aborts. 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.
How severe is CVE-2026-19667?: CVE-2026-19667 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2026-19667 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (45th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-19667?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-19667 published?: CVE-2026-19667 was published on 2026-09-16 and last updated on 2026-09-17.

References

Other CWE-197 vulnerabilities

CVE-2024-43639 — Critical (CVSS 9.8): Windows KDC Proxy Remote Code Execution Vulnerability
CVE-2026-87529 — Critical (CVSS 9.6): Numeric truncation error in Media in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to potentially…
CVE-2020-15202 — Critical (CVSS 9.0): In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `Shard` API in TensorFlow expects the last…
CVE-2024-49018 — High (CVSS 8.8): SQL Server Native Client Remote Code Execution Vulnerability
CVE-2024-43519 — High (CVSS 8.8): Microsoft WDAC OLE DB provider for SQL Server Remote Code Execution Vulnerability
CVE-2024-30009 — High (CVSS 8.8): Windows Routing and Remote Access Service (RRAS) Remote Code Execution Vulnerability

Browse all CWE-197 vulnerabilities →