Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-19033Unauthenticated IXFR deltas are applied to the live zone before TSIG verification

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.

Timeline

  1. ID reserved

    By isc

  2. · 41 days later

    Published

  3. · 1 day later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-19033, by who scored it
Scored byCVSSScoreVector
iscCNA (assigner)3.1Medium6.5CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L
NVDNVD · Awaiting Analysis3.1Medium6.5CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.5.

Affected products

  • ISC · BIND 9

    • affected 9.11.0 – ≤ 9.18.50
    • affected 9.20.0 – ≤ 9.20.27
    • affected 9.21.0 – ≤ 9.21.25
    • affected 9.11.3-S1 – ≤ 9.18.50-S1
    • affected 9.20.9-S1 – ≤ 9.20.27-S1

What to do

Solution: Upgrade to the patched release most closely related to your current version of BIND 9: 9.20.29, 9.21.26, or 9.20.29-S1.

Workaround: No workarounds known.

Exploitation: This flaw was discovered in internal testing. We are not aware of any active exploits.

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-19033 badge
[![CVE-2026-19033](https://cveledger.app/badge/CVE-2026-19033.svg)](https://cveledger.app/cve/CVE-2026-19033)

Record last updated .