In NLnet Labs Unbound up to and including 1.26.0, a 255 length query name with a large TCP response can lead to a heap buffer overflow during the RRSet canonicalisation routine. This is caused by missing to add the first owner name into the buffer length check. A malicious actor operating a malicious name server or tampering with an incoming response to Unbound (canonicalisation happens before DNSSEC validation), can trigger the vulnerability.
CVE-2026-81634
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-16. 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 PROB
- 0%
- EPSS %ILE
- 29%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 16, 2026
Advisory Details (1)
Auto-updated Sep 16, 2026Vendor Advisories for CVE-2026-81634(1)
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.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 34× in last 7d / 34× 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-09-21 06:36 UTCEG score recompute
- 2026-09-21 06:36 UTCVendor advisory
- 2026-09-21 06:36 UTCGHSA enrichment
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-20 18:45 UTCVendor advisory
- 2026-09-20 18:45 UTCGHSA enrichment
- 2026-09-20 06:55 UTCVendor advisory
- 2026-09-20 06:54 UTCGHSA enrichment
- 2026-09-19 18:52 UTCEG score recompute
- 2026-09-19 18:52 UTCVendor advisory
- 2026-09-19 18:52 UTCGHSA enrichment
- 2026-09-19 07:01 UTCEG score recompute
- 2026-09-19 07:01 UTCVendor advisory
- 2026-09-19 07:01 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 19:11 UTCVendor advisory
- 2026-09-18 19:11 UTCGHSA enrichment
- 2026-09-18 07:20 UTCEG score recompute
- 2026-09-18 07:20 UTCVendor advisory
- 2026-09-18 07:20 UTCGHSA enrichment
- 2026-09-17 19:29 UTCVendor advisory
- 2026-09-17 19:29 UTCGHSA enrichment
- 2026-09-17 07:36 UTCVendor advisory
- 2026-09-17 07:36 UTCGHSA enrichment
- 2026-09-16 19:45 UTCGHSA enrichment
Show 9 moreShow fewer
- 2026-09-16 15:25 UTCEG score recompute
- 2026-09-16 15:25 UTCGHSA enrichment
- 2026-09-16 14:36 UTCEG score recompute
- 2026-09-16 14:36 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 09:31 UTCEG score recompute
- 2026-09-16 09:31 UTCGHSA enrichment
- 2026-09-16 08:42 UTCEG score recompute
- 2026-09-16 08:41 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-122
Frequently asked(5)
What is CVE-2026-81634?
When was CVE-2026-81634 disclosed?
Is CVE-2026-81634 actively exploited?
What is the CVSS score of CVE-2026-81634?
How do I remediate CVE-2026-81634?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-81634
Is Your Infrastructure Affected by CVE-2026-81634?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.