PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-96405 NLnet Labs CVE debrief

PatchSiren debrief for CVE-2026-96405: Aggregate DNS name chained pointer decompression work leads to degradation of service. NLnet Labs Unbound up to and including version 1.26.1 has a vulnerability where a malicious actor with recursive-query access and control of an ordinarily delegated authority can exploit it by serving specially crafted replies, degrading Unbound's general performance. The vulnerability exists because Unbound limits compression-pointer traversal for each individual domain-name operation but lacks an aggregate inbound decompression-work budget.

Vendor
NLnet Labs
Product
Unbound
CVSS
MEDIUM 5.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-21
Original CVE updated
2026-10-29
Advisory published
2026-10-21
Advisory updated
2026-10-29

Who should care

DNS administrators, security teams responsible for Unbound deployments, and IT professionals managing critical infrastructure should be aware of this vulnerability and take necessary actions to prevent potential performance degradation attacks.

Why it matters

CVE-2026-96405 is a vulnerability in Unbound DNS servers that can lead to performance degradation when exploited. Defenders should prioritize patching to prevent potential attacks. DNS administrators and security teams managing Unbound deployments should assess exposure and take necessary actions.

  • Potential performance degradation of Unbound DNS servers
  • Increased CPU usage due to maliciously crafted DNS replies
  • Need for patching to prevent exploitation
  • Verification of Unbound version and configuration required

Technical summary

The vulnerability in Unbound DNS server, tracked as CVE-2026-96405, allows a malicious actor with recursive-query access to degrade the server's performance by serving specially crafted DNS replies. This is possible because Unbound does not have an aggregate inbound decompression-work budget, despite limiting compression-pointer traversal for individual domain-name operations. Affected product deployments should be identified, and owners assigned for follow-up. Official advisories and CVE records should be reviewed to validate affected scope, severity, and vendor guidance.

Defensive priority

Defenders should prioritize patching Unbound installations to prevent potential performance degradation attacks. This requires immediate attention from DNS administrators and security teams responsible for Unbound deployments.

Recommended defensive actions

  • Patch Unbound installations to version 1.26.2 or later
  • Monitor Unbound performance for unusual patterns
  • Restrict recursive-query access to trusted sources
  • Review and update DNS security configurations
  • Verify Unbound version and configuration
  • Review compensating controls for exposed systems
  • Track exceptions and retest remediated assets

Evidence notes

The CVE record and source item provide details on the vulnerability, its impact, and affected versions. However, specific details about exploitation or victim organizations are not provided. Defenders should verify Unbound version and configuration, review security settings, and monitor for unusual patterns. Evidence limits suggest focusing on vendor guidance and publicly available information.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-96405 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-96405

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-96405 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-96405

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.