CVE-2026-33608

HIGHNVD 7.47.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
7.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.4HIGHmedium confidence
EG Risk
49
EG Risk 49/100

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 (value × EchelonGraph’s weight)
Severity74% × 45%
The EG Score, 7.4 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 22, 2026

Last Modified

April 24, 2026

References (1)

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
pdns4.4.1-1 ... 5.1.3-1 (53 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
pdns4.7.3-2 ... 5.1.4-1 (41 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pdns4.9.7-1
  • every version up to 4.9.14-0+deb13u1: fixed in 4.9.14-0+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pdns4.9.7-1 ... 5.0.3-1 (6 versions)
  • every version up to 5.0.4-1: fixed in 5.0.4-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 29× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 97 of 223 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 126 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  2. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  3. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  4. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  5. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  6. 2026-10-12 16:13 UTCEG score recompute
  7. 2026-10-11 19:55 UTCEG score recompute
  8. 2026-10-11 17:08 UTCEG score recompute
  9. 2026-10-11 14:36 UTCEG score recompute
  10. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  11. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  12. 2026-10-10 17:33 UTCOSV refresh
  13. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  14. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  15. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  16. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  17. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  19. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  20. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  21. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  22. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  23. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  24. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  25. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.6% · 46th percentile
Show 72 more
  1. 2026-09-21 04:49 UTCOSV refresh
  2. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  3. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  4. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  5. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  6. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  9. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  12. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  13. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  14. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  15. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  16. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  17. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  18. 2026-09-02 02:38 UTCOSV refresh
  19. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  20. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  21. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  22. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  23. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  24. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  25. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  26. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  27. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  28. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  29. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  30. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  31. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  32. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  33. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  34. 2026-08-16 05:58 UTCEG score recompute
  35. 2026-08-16 05:58 UTCGHSA enrichmentGHSA-q6jm-wh7h-j4g3 · GitHub severity HIGH · GitHub CVSS 7.4
  36. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  37. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  38. 2026-08-14 16:10 UTCGHSA enrichmentGHSA-q6jm-wh7h-j4g3 · GitHub severity HIGH · GitHub CVSS 7.4
  39. 2026-08-14 04:18 UTCEG score recompute
  40. 2026-08-14 04:18 UTCGHSA enrichmentGHSA-q6jm-wh7h-j4g3 · GitHub severity HIGH · GitHub CVSS 7.4
  41. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  42. 2026-08-13 08:39 UTCGHSA enrichmentGHSA-q6jm-wh7h-j4g3 · GitHub severity HIGH · GitHub CVSS 7.4
  43. 2026-08-12 18:30 UTCEG score recompute
  44. 2026-08-12 18:30 UTCGHSA enrichmentGHSA-q6jm-wh7h-j4g3 · GitHub severity HIGH · GitHub CVSS 7.4
  45. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  46. 2026-08-11 16:45 UTCEG score recompute
  47. 2026-08-11 16:45 UTCGHSA enrichmentGHSA-q6jm-wh7h-j4g3 · GitHub severity HIGH · GitHub CVSS 7.4
  48. 2026-08-11 02:18 UTCEG score recompute
  49. 2026-08-11 02:18 UTCGHSA enrichmentGHSA-q6jm-wh7h-j4g3 · GitHub severity HIGH · GitHub CVSS 7.4
  50. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  51. 2026-08-10 03:16 UTCGHSA enrichmentGHSA-q6jm-wh7h-j4g3 · GitHub severity HIGH · GitHub CVSS 7.4
  52. 2026-08-09 15:24 UTCEG score recompute
  53. 2026-08-09 15:24 UTCGHSA enrichmentGHSA-q6jm-wh7h-j4g3 · GitHub severity HIGH · GitHub CVSS 7.4
  54. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  55. 2026-08-09 03:32 UTCEG score recompute
  56. 2026-08-09 03:32 UTCGHSA enrichmentGHSA-q6jm-wh7h-j4g3 · GitHub severity HIGH · GitHub CVSS 7.4
  57. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  58. 2026-08-08 12:31 UTCGHSA enrichmentGHSA-q6jm-wh7h-j4g3 · GitHub severity HIGH · GitHub CVSS 7.4
  59. 2026-08-08 00:39 UTCEG score recompute
  60. 2026-08-08 00:39 UTCGHSA enrichmentGHSA-q6jm-wh7h-j4g3 · GitHub severity HIGH · GitHub CVSS 7.4
  61. 2026-08-07 12:47 UTCEG score recompute
  62. 2026-08-07 12:47 UTCGHSA enrichmentGHSA-q6jm-wh7h-j4g3 · GitHub severity HIGH · GitHub CVSS 7.4
  63. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  64. 2026-08-06 11:27 UTCGHSA enrichmentGHSA-q6jm-wh7h-j4g3 · GitHub severity HIGH · GitHub CVSS 7.4
  65. 2026-08-05 23:04 UTCEG score recompute
  66. 2026-08-05 23:03 UTCGHSA enrichmentGHSA-q6jm-wh7h-j4g3 · GitHub severity HIGH · GitHub CVSS 7.4
  67. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  68. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  69. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  70. 2026-08-03 21:14 UTCEG score recompute
  71. 2026-08-03 21:14 UTCGHSA enrichmentGHSA-q6jm-wh7h-j4g3 · GitHub severity HIGH · GitHub CVSS 7.4
  72. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.4% · 31st percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-33608?
CVE-2026-33608 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2026-33608 was made public on April 8, 2026: that is the date its CVE record's CNA, Open-Xchange, gives for when the vulnerability was made public. The CVE record itself was published on April 22, 2026. EchelonGraph's copy of the record carries a last-modified date of April 24, 2026; the record at its source may have been updated since.
Is CVE-2026-33608 actively exploited?
CVE-2026-33608 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
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?
A fix for CVE-2026-33608 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs