CVE-2026-44687

LOWPre-NVD 3.73.7—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.7Exploit: None knownExposed: 0

A fix is available — apply it.

In NLnet Labs Unbound 1.13.2 up to and including 1.25.1, stub or forward zones where the name is below an intermediate labed below a DNSSEC signed zone could be shadowed by the intermediate label's secure NXDOMAIN answer from the parent. This is caused by an off-by-one error in 'harden-below-nxdomain' logic; enabled by default. It effectively bypasses the configuration and the configured stub/forward zone is never contacted. 'harden-below-nxdomain' does an upward DNS cache walk together with a delegation point guard that does not allow NXDOMAIN synthesis above stub/forward zones. The guard tests the domain name but before stripping a label. This results in an iteration where the domain name equals the configured stub/forward zone apex that passes the guard, strips one more label, and probes the cache at the apex's immediate public parent. If that parent has a cached DNSSEC-secure NXDOMAIN, which it will for any private namespace nested two or more labels under a signed public name, the walk returns it and the configured stub/forward upstream is never contacted. This can only be triggered by the query for the intermediate label (between the stub/forward apex and the DNSSEC parent zone).

CVSS v3
3.7
EG Score
3.7(medium)
EG Risk
17(Track)
EG Risk 17/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
Severity37% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

July 22, 2026

Last Modified

July 24, 2026

References (1)

Vendor Advisories for CVE-2026-44687(3)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
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 12× in last 7d / 48× 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 102 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-44687?
CVE-2026-44687 is a low vulnerability published on July 22, 2026. In NLnet Labs Unbound 1.13.2 up to and including 1.25.1, stub or forward zones where the name is below an intermediate labed below a DNSSEC signed zone could be shadowed by the intermediate label's secure NXDOMAIN answer from the parent. This is caused by an off-by-one error in…
When was CVE-2026-44687 disclosed?
CVE-2026-44687 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-44687 actively exploited?
CVE-2026-44687 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 87.7% of all scored CVEs.
What is the CVSS score of CVE-2026-44687?
CVE-2026-44687 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-44687?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44687, 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-44687

Explore →

Is Your Infrastructure Affected by CVE-2026-44687?

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

Start Free Scan →Browse All CVEs