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
72%
KEV
Not listed

Published

March 25, 2026

Last Modified

July 23, 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(23)

Vendor / EcosystemFixed in / PatchReleasedSource
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.18-32:9.18.29-4.el9_6.32026-06-11redhat
redhatbind9.16-32:9.16.23-0.7.el8_6.102026-06-11redhat
redhatbind-32:9.16.23-18.el9_4.112026-06-11redhat
ubuntubind9-utils (1:9.20.11-1ubuntu2.2) @ questing2026-06-11ubuntu
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.36-8.el8_8.92026-05-11redhat
redhatbind-32:9.11.26-4.el8_4.92026-05-11redhat
redhatbind-32:9.11.4-26.P2.el7_9.202026-04-28redhat
redhatbind-32:9.8.2-0.68.rc1.el6_10.182026-04-28redhat
redhatbind-32:9.18.33-10.el10_1.32026-04-15redhat
redhatbind-32:9.11.36-16.el8_10.72026-04-15redhat
redhatbind-32:9.16.23-34.el9_7.22026-04-14redhat
redhatbind9.16-32:9.16.23-0.22.el8_10.52026-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.

Weakness Classification(2)

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

Additional Vendor Advisories

(4)

Data Freshness Timeline

(refreshed 15× in last 7d / 46× 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 128 total refreshes for this CVE.

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

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 July 23, 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 27.6% 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

Explore the affected products and dependency analysis for 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.