CVE-2026-44690

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH 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 — 5 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

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

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(high)
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
5%
KEV
Not listed

Published

July 22, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Jul 22, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-44690(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 21× 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.

  1. 2026-07-27 03:36 UTCVendor advisory
  2. 2026-07-27 03:36 UTCGHSA enrichment
  3. 2026-07-26 15:33 UTCEG score recompute
  4. 2026-07-26 15:33 UTCVendor advisory
  5. 2026-07-26 15:33 UTCGHSA enrichment
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-26 03:29 UTCEG score recompute
  9. 2026-07-26 03:29 UTCVendor advisory
  10. 2026-07-26 03:29 UTCGHSA enrichment
  11. 2026-07-25 14:18 UTCEPSS rescore
  12. 2026-07-24 14:17 UTCEPSS rescore
  13. 2026-07-23 14:18 UTCEPSS rescore
  14. 2026-07-23 03:15 UTCEG score recompute
  15. 2026-07-22 22:03 UTCEG score recompute
  16. 2026-07-22 22:03 UTCGHSA enrichment
  17. 2026-07-22 19:11 UTCEG score recompute
  18. 2026-07-22 19:11 UTCGHSA enrichment
  19. 2026-07-22 14:58 UTCEG score recompute
  20. 2026-07-22 13:17 UTCEG score recompute
  21. 2026-07-22 13:17 UTCMITRE cvelistV5first tracked

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.3% 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

Explore the affected products and dependency analysis for 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.