CVE-2026-44690

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-47669 (ENISA EUVD) · GHSA-jwg4-375h-655h (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
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.2%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In NLnet Labs Unbound 1.7.0 up to and including 1.25.1, insufficient validation of the RRSIG.Labels field combined with premature cache writes during RFC 8198 aggressive NSEC processing leads to cache poisoning that permits a malicious actor controlling a single delegated zone to poison arbitrary sibling zones under NSEC-signed parent domains. A malicious actor with one registered domain under an NSEC-signed TLD can serve malicious insecure DNS responses for unrelated sibling domains (sharing the same parent zone). Arbitrary delegations that do not exist under the parent domain and are covered by the parent's NSEC chain can be brought into insecure existence by fraudulent wildcard DS records (less labels than expected, unknown algorithm) from the malicious sibling domain. This allows the malicious actor to inject insecure wildcard records for those delegations.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 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.2%
EPSS %ILE
4th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-08). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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

July 22, 2026

Last Modified

October 24, 2026

Advisory Details (1)

Auto-updated Jul 22, 2026
Patch available.

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuunbound-host (1.5.8-1ubuntu1.1+esm5) @ xenial2026-11-01ubuntu
redhatopenshift/ose-rhel-coreos-9:4.22.9.8.202608251819-02026-09-01redhat
redhatunbound-0:1.24.2-7.el10_2.42026-08-17redhat
redhatunbound-0:1.16.2-5.14.el8_102026-08-17redhat
redhatunbound-0:1.24.2-3.el9_8.42026-08-17redhat
redhatunbound-main-1.25.2-0.1.hum12026-07-22redhat

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

(7 across 7 ecosystems)
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
unbound—
  • 1.7.0 up to 1.25.2-r0: fixed in 1.25.2-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
unbound—
  • 1.7.0 up to 1.25.2-r0: fixed in 1.25.2-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
unbound—
  • 1.7.0 up to 1.25.2-r0: fixed in 1.25.2-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
unbound1.13.1-1 ... 1.25.2-1 (47 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
unbound1.17.1-2 ... 1.26.2-1 (27 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
unbound1.22.0-2 ... 1.26.0-2 (15 versions)
  • every version up to 1.26.1-0+deb13u1: fixed in 1.26.1-0+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
unbound1.22.0-2 ... 1.25.1-1 (9 versions)
  • every version up to 1.25.2-1: fixed in 1.25.2-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 38× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 373 rows 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. None are among the latest 100 rows. The 273 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-11-11 16:39 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  5. 2026-11-08 21:25 UTCEchelonGraph re-scored
  6. 2026-11-08 21:25 UTCVendor advisory
  7. 2026-11-08 21:25 UTCGHSA enrichmentGHSA-jwg4-375h-655h · GitHub severity HIGH · GitHub CVSS 7.5
  8. 2026-11-08 16:39 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-11-05 16:37 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  14. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-11-01 05:27 UTCEchelonGraph re-scored
  17. 2026-11-01 05:27 UTCVendor advisory
  18. 2026-11-01 05:27 UTCGHSA enrichmentGHSA-jwg4-375h-655h · GitHub severity HIGH · GitHub CVSS 7.5
  19. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  22. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  24. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
Show 75 more
  1. 2026-10-25 14:27 UTCEchelonGraph re-scored
  2. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-10-24 13:29 UTCEchelonGraph re-scored
  4. 2026-10-24 13:29 UTCVendor advisory
  5. 2026-10-24 13:29 UTCGHSA enrichmentGHSA-jwg4-375h-655h · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  7. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  8. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-10-18 03:39 UTCEchelonGraph re-scored
  13. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-10-17 13:54 UTCEchelonGraph re-scored
  15. 2026-10-17 13:54 UTCVendor advisory
  16. 2026-10-17 13:53 UTCGHSA enrichmentGHSA-jwg4-375h-655h · GitHub severity HIGH · GitHub CVSS 7.5
  17. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  19. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  20. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  21. 2026-10-12 16:05 UTCEchelonGraph re-scored
  22. 2026-10-11 19:47 UTCEchelonGraph re-scored
  23. 2026-10-11 17:01 UTCEchelonGraph re-scored
  24. 2026-10-11 14:27 UTCEchelonGraph re-scored
  25. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  26. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  27. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  28. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  29. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  30. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  31. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  32. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  33. 2026-10-04 13:27 UTCEchelonGraph re-scored
  34. 2026-10-04 13:27 UTCVendor advisory
  35. 2026-10-04 13:27 UTCGHSA enrichmentGHSA-jwg4-375h-655h · GitHub severity HIGH · GitHub CVSS 7.5
  36. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  37. 2026-10-03 03:34 UTCEchelonGraph re-scored
  38. 2026-10-03 03:34 UTCVendor advisory
  39. 2026-10-03 03:34 UTCGHSA enrichmentGHSA-jwg4-375h-655h · GitHub severity HIGH · GitHub CVSS 7.5
  40. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  41. 2026-10-01 06:29 UTCEchelonGraph re-scored
  42. 2026-10-01 06:29 UTCVendor advisory
  43. 2026-10-01 06:29 UTCGHSA enrichmentGHSA-jwg4-375h-655h · GitHub severity HIGH · GitHub CVSS 7.5
  44. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  45. 2026-09-28 05:18 UTCEchelonGraph re-scored
  46. 2026-09-28 05:18 UTCVendor advisory
  47. 2026-09-28 05:18 UTCGHSA enrichmentGHSA-jwg4-375h-655h · GitHub severity HIGH · GitHub CVSS 7.5
  48. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  49. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  50. 2026-09-24 02:07 UTCEchelonGraph re-scored
  51. 2026-09-24 02:07 UTCVendor advisory
  52. 2026-09-24 02:07 UTCGHSA enrichmentGHSA-jwg4-375h-655h · GitHub severity HIGH · GitHub CVSS 7.5
  53. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  54. 2026-09-23 12:03 UTCVendor advisory
  55. 2026-09-23 12:03 UTCGHSA enrichmentGHSA-jwg4-375h-655h · GitHub severity HIGH · GitHub CVSS 7.5
  56. 2026-09-22 23:59 UTCEchelonGraph re-scored
  57. 2026-09-22 23:59 UTCVendor advisory
  58. 2026-09-22 23:59 UTCGHSA enrichmentGHSA-jwg4-375h-655h · GitHub severity HIGH · GitHub CVSS 7.5
  59. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  60. 2026-09-20 02:05 UTCEchelonGraph re-scored
  61. 2026-09-20 02:05 UTCVendor advisory
  62. 2026-09-20 02:05 UTCGHSA enrichmentGHSA-jwg4-375h-655h · GitHub severity HIGH · GitHub CVSS 7.5
  63. 2026-09-18 22:41 UTCEchelonGraph re-scored
  64. 2026-09-18 22:41 UTCVendor advisory
  65. 2026-09-18 22:41 UTCGHSA enrichmentGHSA-jwg4-375h-655h · GitHub severity HIGH · GitHub CVSS 7.5
  66. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  67. 2026-09-18 03:11 UTCEchelonGraph re-scored
  68. 2026-09-18 03:11 UTCVendor advisory
  69. 2026-09-18 03:11 UTCGHSA enrichmentGHSA-jwg4-375h-655h · GitHub severity HIGH · GitHub CVSS 7.5
  70. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  71. 2026-09-17 02:12 UTCEchelonGraph re-scored
  72. 2026-09-17 02:12 UTCVendor advisory
  73. 2026-09-17 02:12 UTCGHSA enrichmentGHSA-jwg4-375h-655h · GitHub severity HIGH · GitHub CVSS 7.5
  74. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  75. 2026-09-16 07:04 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-44690?
CVE-2026-44690 is a high-severity vulnerability; its CVE record was published on July 22, 2026. In NLnet Labs Unbound 1.7.0 up to and including 1.25.1, insufficient validation of the RRSIG.Labels field combined with premature cache writes during RFC 8198 aggressive NSEC processing leads to cache poisoning that permits a malicious actor controlling a single delegated zone to poison arbitrary…
When was CVE-2026-44690 made public?
CVE-2026-44690 was made public on July 22, 2026: that is the date its CVE record's CNA, NLnet Labs, gives for when the vulnerability was made public. The CVE record itself was published on July 22, 2026. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-44690 actively exploited?
CVE-2026-44690 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44690?
CVE-2026-44690 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-44690?
A fix for CVE-2026-44690 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44690 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-44690?

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