CVE-2026-1519

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-03-25. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

If a BIND resolver is performing DNSSEC validation and encounters a maliciously crafted zone, the resolver may consume excessive CPU. Authoritative-only servers are generally unaffected, although there are circumstances where authoritative servers may make recursive queries (see: https://kb.isc.org/docs/why-does-my-authoritative-server-make-recursive-queries). This issue affects BIND 9 versions 9.11.0 through 9.16.50, 9.18.0 through 9.18.46, 9.20.0 through 9.20.20, 9.21.0 through 9.21.19, 9.11.3-S1 through 9.16.50-S1, 9.18.11-S1 through 9.18.46-S1, and 9.20.9-S1 through 9.20.20-S1.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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 computed
Severity75% × 45%
Exploitation2% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
75%
KEV
Not listed

Published

March 25, 2026

Last Modified

September 17, 2026

Advisory Details (5)

Auto-updated Jun 12, 2026
Patch available.
generic Patch Available

[SECURITY] [DLA 4529-1] bind9 security update

https://lists.debian.org/debian-lts-announce/2026/04/msg00008.html
generic

CVE-2026-1519: Excessive NSEC3 iterations cause high CPU load during insecure delegation validation

https://kb.isc.org/docs/cve-2026-1519
generic

Index of /isc/bind9/9.21.20

https://downloads.isc.org/isc/bind9/9.21.20
generic

Index of /isc/bind9/9.20.21

https://downloads.isc.org/isc/bind9/9.20.21
generic

Index of /isc/bind9/9.18.47

https://downloads.isc.org/isc/bind9/9.18.47

Patch Availability(27)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhcos-418.94.202609031320-02026-09-17redhat
ubuntubind9-utils (1:9.20.11-1ubuntu2.2) @ questing2026-09-17ubuntu
redhatrhcos-416.94.202609011112-02026-09-10redhat
redhatrhcos-417.94.202608250221-02026-09-03redhat
redhatrhcos-415.92.202607210244-02026-07-31redhat
redhatrhcos-413.92.202607141229-02026-07-23redhat
redhatrhcos-414.92.202607031936-02026-07-20redhat
redhatrhcos-412.86.202606251120-02026-07-09redhat
redhatrhcos-4.19.9.6.202606241344-02026-07-02redhat
redhatbind-32:9.16.23-11.el9_2.102026-06-24redhat
redhatbind9.16-32:9.16.23-0.7.el8_6.102026-06-11redhat
redhatbind9.18-32:9.18.29-4.el9_6.32026-06-11redhat
redhatbind-32:9.16.23-18.el9_4.112026-06-11redhat
redhatbind9.16-32:9.16.23-0.14.el8_8.82026-06-10redhat
redhatbind-32:9.18.33-4.el10_0.32026-06-09redhat
redhatbind-32:9.16.23-31.el9_6.32026-06-08redhat
redhatbind-32:9.11.36-3.el8_6.122026-05-11redhat
redhatbind-32:9.11.26-4.el8_4.92026-05-11redhat
redhatbind-32:9.11.36-8.el8_8.92026-05-11redhat
redhatbind-32:9.8.2-0.68.rc1.el6_10.182026-04-28redhat
redhatbind-32:9.11.4-26.P2.el7_9.202026-04-28redhat
redhatbind-32:9.11.36-16.el8_10.72026-04-15redhat
redhatbind-32:9.18.33-10.el10_1.32026-04-15redhat
redhatbind9.16-32:9.16.23-0.22.el8_10.52026-04-14redhat
redhatbind-32:9.16.23-34.el9_7.22026-04-14redhat
redhatbind9.18-32:9.18.29-5.el9_7.42026-04-13redhat
redhatbind-main-9.18.48-1.hum12026-04-07redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(9 across 9 ecosystems)
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
bind9.18.47-r0
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
bind9.18.47-r0
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
bind9.20.21-r0
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
bind9.20.21-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
bind9.20.21-r0
Debian:11(1)
PackageVulnerable rangeFixed inDependents
bind91:9.16.15-1 ... 1:9.16.50-1~deb11u4 (16 versions)1:9.16.50-1~deb11u5
Debian:12(1)
PackageVulnerable rangeFixed inDependents
bind91:9.18.12-1 ... 1:9.18.44-1~deb12u1 (14 versions)1:9.18.47-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
bind91:9.20.11-4 ... 1:9.20.20-1~bpo12+1 (12 versions)1:9.20.21-1~deb13u1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
bind91:9.20.11-4 ... 1:9.20.21-1~deb13u1~bpo12+1 (14 versions)1:9.20.21-1

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 11× in last 7d / 51× 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.

Showing the most recent 100 of 246 total refreshes for this CVE.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-17 12:19 UTCEG score recompute
  3. 2026-09-17 12:19 UTCVendor advisory
  4. 2026-09-17 12:19 UTCGHSA enrichment
  5. 2026-09-17 12:11 UTCEG score recompute
  6. 2026-09-17 12:11 UTCVendor advisory
  7. 2026-09-17 12:11 UTCGHSA enrichment
  8. 2026-09-16 14:07 UTCEPSS rescore
  9. 2026-09-16 05:14 UTCEPSS rescore
  10. 2026-09-13 16:46 UTCEPSS rescore
  11. 2026-09-12 15:00 UTCEPSS rescore
  12. 2026-09-11 14:52 UTCEPSS rescore
  13. 2026-09-11 09:36 UTCEPSS rescore
  14. 2026-09-10 13:22 UTCEG score recompute
  15. 2026-09-10 13:22 UTCVendor advisory
  16. 2026-09-10 13:22 UTCGHSA enrichment
  17. 2026-09-10 12:28 UTCEG score recompute
  18. 2026-09-10 12:28 UTCVendor advisory
  19. 2026-09-10 12:28 UTCGHSA enrichment
  20. 2026-09-10 09:34 UTCEPSS rescore
  21. 2026-09-08 22:00 UTCEPSS rescore
  22. 2026-09-07 16:01 UTCEPSS rescore
  23. 2026-09-06 13:47 UTCEPSS rescore
  24. 2026-09-04 13:30 UTCEG score recompute
  25. 2026-09-04 13:30 UTCVendor advisory
Show 75 more
  1. 2026-09-04 13:30 UTCGHSA enrichment
  2. 2026-09-04 12:25 UTCEG score recompute
  3. 2026-09-04 12:25 UTCVendor advisory
  4. 2026-09-04 12:24 UTCGHSA enrichment
  5. 2026-09-04 05:06 UTCEPSS rescore
  6. 2026-09-02 14:11 UTCEPSS rescore
  7. 2026-09-01 13:53 UTCEPSS rescore
  8. 2026-09-01 12:24 UTCEG score recompute
  9. 2026-09-01 12:24 UTCVendor advisory
  10. 2026-09-01 12:23 UTCGHSA enrichment
  11. 2026-09-01 04:39 UTCEPSS rescore
  12. 2026-08-30 19:17 UTCEPSS rescore
  13. 2026-08-30 01:22 UTCEPSS rescore
  14. 2026-08-28 21:41 UTCEPSS rescore
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-26 14:46 UTCEPSS rescore
  17. 2026-08-25 13:48 UTCEPSS rescore
  18. 2026-08-25 12:22 UTCEG score recompute
  19. 2026-08-25 12:22 UTCVendor advisory
  20. 2026-08-25 12:22 UTCGHSA enrichment
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-21 12:32 UTCEG score recompute
  24. 2026-08-21 12:32 UTCVendor advisory
  25. 2026-08-21 12:32 UTCGHSA enrichment
  26. 2026-08-20 22:55 UTCEPSS rescore
  27. 2026-08-19 17:03 UTCEPSS rescore
  28. 2026-08-18 13:48 UTCEPSS rescore
  29. 2026-08-17 13:47 UTCEPSS rescore
  30. 2026-08-16 14:56 UTCEPSS rescore
  31. 2026-08-16 10:23 UTCEG score recompute
  32. 2026-08-16 10:23 UTCVendor advisory
  33. 2026-08-16 10:23 UTCGHSA enrichment
  34. 2026-08-16 02:14 UTCEPSS rescore
  35. 2026-08-15 01:30 UTCEPSS rescore
  36. 2026-08-14 19:34 UTCVendor advisory
  37. 2026-08-14 19:34 UTCGHSA enrichment
  38. 2026-08-14 06:42 UTCEG score recompute
  39. 2026-08-14 06:42 UTCVendor advisory
  40. 2026-08-14 06:42 UTCGHSA enrichment
  41. 2026-08-13 22:00 UTCEPSS rescore
  42. 2026-08-12 20:57 UTCEG score recompute
  43. 2026-08-12 20:57 UTCVendor advisory
  44. 2026-08-12 20:57 UTCGHSA enrichment
  45. 2026-08-12 13:50 UTCEPSS rescore
  46. 2026-08-11 21:00 UTCEG score recompute
  47. 2026-08-11 21:00 UTCVendor advisory
  48. 2026-08-11 21:00 UTCGHSA enrichment
  49. 2026-08-11 13:42 UTCEPSS rescore
  50. 2026-08-11 04:03 UTCEG score recompute
  51. 2026-08-11 04:03 UTCVendor advisory
  52. 2026-08-11 04:03 UTCGHSA enrichment
  53. 2026-08-11 00:00 UTCEPSS rescore
  54. 2026-08-10 06:56 UTCVendor advisory
  55. 2026-08-10 06:56 UTCGHSA enrichment
  56. 2026-08-09 18:35 UTCEG score recompute
  57. 2026-08-09 18:35 UTCVendor advisory
  58. 2026-08-09 18:35 UTCGHSA enrichment
  59. 2026-08-09 13:46 UTCEPSS rescore
  60. 2026-08-09 06:15 UTCEG score recompute
  61. 2026-08-09 06:15 UTCVendor advisory
  62. 2026-08-09 06:15 UTCGHSA enrichment
  63. 2026-08-08 16:37 UTCEPSS rescore
  64. 2026-08-08 04:54 UTCVendor advisory
  65. 2026-08-08 04:54 UTCGHSA enrichment
  66. 2026-08-07 16:34 UTCEG score recompute
  67. 2026-08-07 16:34 UTCVendor advisory
  68. 2026-08-07 16:34 UTCGHSA enrichment
  69. 2026-08-06 19:00 UTCEG score recompute
  70. 2026-08-06 19:00 UTCVendor advisory
  71. 2026-08-06 19:00 UTCGHSA enrichment
  72. 2026-08-06 13:46 UTCEPSS rescore
  73. 2026-08-06 01:03 UTCEG score recompute
  74. 2026-08-06 01:03 UTCVendor advisory
  75. 2026-08-06 01:03 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-1519?
CVE-2026-1519 is a high vulnerability published on March 25, 2026. If a BIND resolver is performing DNSSEC validation and encounters a maliciously crafted zone, the resolver may consume excessive CPU. Authoritative-only servers are generally unaffected, although there are circumstances where authoritative servers may make recursive queries (see:…
When was CVE-2026-1519 disclosed?
CVE-2026-1519 was first published in the National Vulnerability Database on March 25, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-1519 actively exploited?
CVE-2026-1519 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 25.3% of all scored CVEs.
What is the CVSS score of CVE-2026-1519?
CVE-2026-1519 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-1519?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-1519, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-1519

Explore →

Is Your Infrastructure Affected by CVE-2026-1519?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.