cve.bz

CVE-2026-109125 nlnet labs unbound: Observable Behavioral Discrepancy

5.3 mediumEPSS 0.2%

Medium (5.3) in nlnet labs unbound. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In NLnet Labs Unbound up to and including version 1.26.1, an observable cache-level side-channel can be exposed with 'unwanted-reply-threshold > 0' configurations (not a default configuration). If a response-like UDP datagram reaches the upstream source port currently used by a recursive query, but its TXID does not match any pending query, Unbound counts the packet as an unwanted reply. When the accumulated count reaches the configured threshold, Unbound clears the worker's RRset cache and message cache. This cache clear action does not destroy the current upstream UDP pending query. Therefore, an external observer can distinguish whether a candidate port matches the current upstream source port by checking whether an existing cached item has been cleared. This is a cache side-channel vulnerability that can be used to probe the upstream source port. Although the attack is not feasible on default configurations and the suggested value (10 million) makes it an ureliable attack on a public resolver, in scenarios where the attacker can keep a concurrent query window alive, the attacker can first filter the source port and then perform birthday-style guessing against the TXID, making cache poisoning a feasible attack path.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-205 Observable Behavioral Discrepancy
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-109125 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-109125?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-109125?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-109125 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • nlnet labs:unbound

Versions

From the CNA's record in the CVE List.

ProductAffected
NLnet Labs Unboundbefore 1.26.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12unboundno fix listedDEBIAN-CVE-2026-109125
Debian13unbound1.26.2-0+deb13u1DEBIAN-CVE-2026-109125
Debian14unbound1.26.2-1DEBIAN-CVE-2026-109125
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 5 moreunboundno fix listedUBUNTU-CVE-2026-109125
openSUSETumbleweedunbound1.26.2-1.1openSUSE-SU-2026:12257-1
Azure Linux3unbound1.26.2-1AZL-110528

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Attack patterns (CAPEC)

  • CAPEC-541 Application Fingerprinting Severity: Low
  • CAPEC-580 System Footprinting Likelihood: Low · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON