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.
CVE-2026-19033
Score 6.5 from GitHub Security Advisory published 2026-09-16. a secondary CVSS source baseline 6.5; 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
- 6.5
- EG Score
- 6.5(high)
- EG Risk
- 29(Track)EG Risk 29/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 computedSeverity65% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 11%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 17, 2026
Advisory Details (3)
Auto-updated Sep 16, 2026CVE-2026-19033: Unauthenticated IXFR deltas are applied to the live zone before TSIG verification
https://kb.isc.org/docs/cve-2026-19033Vendor Advisories for CVE-2026-19033(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 12× in last 7d / 12× 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 21:14 UTCEG score recompute
- 2026-09-18 21:14 UTCGHSA enrichment
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-17 18:26 UTCEG score recompute
- 2026-09-17 18:26 UTCGHSA enrichment
- 2026-09-17 18:00 UTCEG score recompute
- 2026-09-17 18:00 UTCGHSA enrichment
- 2026-09-16 19:32 UTCEG score recompute
- 2026-09-16 19:32 UTCGHSA enrichment
- 2026-09-16 15:20 UTCEG score recompute
- 2026-09-16 14:26 UTCEG score recompute
- 2026-09-16 14:25 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-19033?
When was CVE-2026-19033 disclosed?
Is CVE-2026-19033 actively exploited?
What is the CVSS score of CVE-2026-19033?
How do I remediate CVE-2026-19033?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-19033
Is Your Infrastructure Affected by CVE-2026-19033?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.