Skip to main content
VulnerabilityPublished Updated

CVE-2026-19033: ISC BIND 9 · Acceptance of Extraneous Untrusted Data With Trusted Data

Affects ISC BIND 9Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 31 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
ISCBIND 9Affected
  • >=9.11.0 <=9.18.50
  • >=9.20.0 <=9.20.27
  • >=9.21.0 <=9.21.25
  • >=9.11.3-S1 <=9.18.50-S1
  • >=9.20.9-S1 <=9.20.27-S1
Fixed in–
GitHubisc/bind9pkg:github/isc/bind9Other threatsAffected
  • >=9.11.0 <=9.18.50
  • >=9.20.0 <=9.20.27
  • >=9.21.0 <=9.21.25
  • >=9.11.3-S1 <=9.18.50-S1
  • >=9.20.9-S1 <=9.20.27-S1
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, administrators should consider restricting or monitoring multi-message TCP IXFR transfers with TSIG or apply any recommended vendor mitigations once published.

Description

For a secondary zone with transfers restricted by TSIG, `named` may start to serve the data provided in a zone transfer before the final message with the TSIG signature arrives. This could allow an attacker that does not actually possess a valid TSIG signature to send unauthorized zone contents to a secondary server. Although no TSIG signature ever arrives, `named` does not rollback to the pre-transfer state. To exploit the vulnerability, the transfer must be a multi-message TCP IXFR, as described by RFC 8945. 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.

References

Community reviews

Loading reviews…