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.
CVE-2026-44690
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.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- 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 computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 4.8%
- KEV
- Not listed
Published
July 22, 2026
Last Modified
July 24, 2026
Advisory Details (1)
Auto-updated Jul 22, 2026Vendor 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 10× in last 7d / 10× 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.
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:15 UTCEG score recompute
- 2026-07-22 22:03 UTCEG score recompute
- 2026-07-22 22:03 UTCGHSA enrichment
- 2026-07-22 19:11 UTCEG score recompute
- 2026-07-22 19:11 UTCGHSA enrichment
- 2026-07-22 14:58 UTCEG score recompute
- 2026-07-22 13:17 UTCEG score recompute
- 2026-07-22 13:17 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-345
Frequently asked(5)
What is CVE-2026-44690?
When was CVE-2026-44690 disclosed?
Is CVE-2026-44690 actively exploited?
What is the CVSS score of CVE-2026-44690?
How do I remediate CVE-2026-44690?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-44690
Is Your Infrastructure Affected by CVE-2026-44690?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.