CVE-2026-44690

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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, ghsa, secondary
Trending — 4 sources updated 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: 0%CVSS: 7.5Exploit: None knownExposed: 0

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.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%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

July 22, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Jul 22, 2026
No patch confirmed yet.
generic
https://www.nlnetlabs.nl/downloads/unbound/CVE-2026-44690.txt

Vendor Advisories for CVE-2026-44690(7)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhcos-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

(5 across 5 ecosystems)
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
unbound—1.25.2-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
unbound1.13.1-1 ... 1.25.2-1 (47 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
unbound1.17.1-2 ... 1.26.0-2 (25 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
unbound1.22.0-2 ... 1.26.0-2 (15 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
unbound1.22.0-2 ... 1.25.1-1 (9 versions)1.25.2-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 30× in last 7d / 131× 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 274 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-44690?
CVE-2026-44690 is a high vulnerability 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 disclosed?
CVE-2026-44690 was first published in the National Vulnerability Database on July 22, 2026, with the most recent update on July 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-44690 actively exploited?
CVE-2026-44690 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.8% of all scored CVEs.
What is the CVSS score of CVE-2026-44690?
CVE-2026-44690 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-44690?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44690, 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-44690

Explore →

Is Your Infrastructure Affected by CVE-2026-44690?

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

Start Free Scan →Browse All CVEs