CVE-2026-33608

HIGHNVD 7.47.4
EchelonGraph scoreMEDIUM confidence

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-04-22. NVD baseline CVSS 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.4Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An attacker can send a notify request that causes a new secondary domain to be added to the bind backend, but causes said backend to update its configuration to an invalid one, leading to the backend no longer able to run on the next restart, requiring manual operation to fix it.

CVSS v3
7.4
EG Score
7.4(medium)
EPSS
30.5%
KEV
Not listed

Published

April 22, 2026

Last Modified

April 24, 2026

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 41× 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 123 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-33608?
CVE-2026-33608 is a high vulnerability published on April 22, 2026. An attacker can send a notify request that causes a new secondary domain to be added to the bind backend, but causes said backend to update its configuration to an invalid one, leading to the backend no longer able to run on the next restart, requiring manual operation to fix it.
When was CVE-2026-33608 disclosed?
CVE-2026-33608 was first published in the National Vulnerability Database on April 22, 2026, with the most recent update on April 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33608 actively exploited?
CVE-2026-33608 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 30.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-33608?
CVE-2026-33608 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-33608?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33608, 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-33608

Explore →

Is Your Infrastructure Affected by CVE-2026-33608?

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