Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted DNS response to recursor
-
ExploitOPT RR carries non-root owner name
-
ExecutionMissing owner-name validation accepts it
-
ImpactECS hardening controls bypassed
Vulnerability Assessment
| Exploitation Conditions | Exploitation is only meaningful when EDNS Client Subnet handling is active on the recursor (operator-enabled, e.g. use-incoming-edns-subnet), since the bypassed control is the ECS hardening logic - this is a non-default deployment mode and the primary limiting factor. The attacker must additionally be able to supply DNS messages containing a crafted EDNS OPT pseudo-record whose owner name is not the root label '.', which normally requires the ability to return responses the resolver processes (a malicious/attacker-controlled authoritative server or on-path position). The impact is limited to defeating a hardening mechanism rather than directly achieving code execution or full cache poisoning. |
| Impact | No CVSS vector, EPSS score, KEV entry, or POC is provided in the input for CVE-2026-85556, so quantitative exploitation signals are entirely absent and risk must be inferred from the advisory text alone. The vendor (PowerDNS Security Advisory 2026-12) classifies this advisory as containing three High-severity CVEs with the remainder rated Medium or Low; the nature of this specific issue - 'Missing OPT RR owner-name validation bypasses ECS hardening' - is consistent with a lower-severity hardening-bypass rather than one of the three High items (which are more plausibly the DoS and DNSSEC/cache-poisoning issues CVE-2026-73206, CVE-2026-73205, and CVE-2026-85555). This is a defense-in-depth control bypass: the recursor fails to validate that an EDNS OPT pseudo-record carries the required root ('.') owner name (per RFC 6891), allowing the EDNS Client Subnet (ECS) hardening protections to be evaded. Because exploitation is only meaningful when ECS handling is active (a non-default, operator-enabled configuration), real-world exposure is narrower than the product's overall deployment footprint. Exploitation status: no public exploit identified at time of analysis. Authentication requirements are not confirmed from available data because no CVSS vector was supplied; the issue is reachable by remote attackers able to deliver crafted DNS messages to the resolver. Net assessment: a genuine but low-urgency fix - patch during normal maintenance, prioritizing it only if use-incoming-edns-subnet / ECS is enabled. |
| Exploit ScenarioDerived | An attacker positioned to return DNS responses to the recursor (e.g., a malicious or attacker-influenced authoritative server, or an on-path responder) crafts a reply whose EDNS OPT record uses a non-root owner name instead of the mandatory root label. Because the recursor does not validate the OPT RR owner name, the ECS hardening logic is bypassed, letting the attacker influence how client-subnet information is processed. No public exploit code is known, and the attack is only relevant on resolvers with ECS handling enabled. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
PowerDNS Recursor can have its EDNS Client Subnet (ECS) hardening bypassed by a crafted EDNS OPT pseudo-record whose owner name is not the root label, weakening the intended ECS restrictions rather than directly enabling code execution or full cache poisoning. The issue affects 5.3.x releases before 5.3.12 and 5.4.x releases before 5.4.8, and exploitation is only meaningful where incoming ECS handling is enabled (for example use-incoming-edns-subnet), a non-default deployment mode. No public exploit code, KEV entry, or EPSS score was provided; our independent assessment is CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N, and no public exploit was identified at time of analysis.
RemediationAI
Upgrade to PowerDNS Recursor 5.3.12 or later in the 5.3.x train, or 5.4.8 or later in the 5.4.x train; these are the vendor-released fixed versions for SA-2026-12. If upgrading is not immediately possible, disable incoming ECS handling (for example, remove use-incoming-edns-subnet) because this bypass only matters when ECS hardening is active; the trade-off is loss of ECS-aware responses and any subnet-based policy behavior. Restrict recursor access to trusted clients and monitor EDNS/ECS traffic as supplemental controls, but do not treat those as a fix for the missing OPT owner-name validation. See the vendor advisory at https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2026-12.html and the 5.3.12 and 5.4.8 changelogs at https://doc.powerdns.com/recursor/changelog/5.3.html#change-5.3.12 and https://doc.powerdns.com/recursor/changelog/5.4.html#change-5.4.8.
Affected ProductsAI
PowerDNS Recursor 5.3.x before 5.3.12 and 5.4.x before 5.4.8 are the affected versions identified by the vendor advisory. The supplied data contains no CPE identifiers, so no CPE match strings can be listed. Vendor changelogs are at https://doc.powerdns.com/recursor/changelog/5.3.html#change-5.3.12 and https://doc.powerdns.com/recursor/changelog/5.4.html#change-5.4.8, with the full advisory at https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2026-12.html. PowerDNS also points to its EOL policy at https://docs.powerdns.com/recursor/appendices/EOL.html for older trains.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
PowerDNS Recursor is a recursive DNS server. EDNS(0) uses an OPT pseudo-RR in the additional section, and RFC 6891 requires the OPT owner name to be the root label ('.'); ECS is carried as an EDNS option and PowerDNS applies hardening around ECS handling. This CVE is a missing validation of the OPT RR owner name, so a crafted DNS message with an OPT owner name other than '.' can bypass that ECS hardening. The input does not assign a CWE, but the root cause is an input-validation gap in EDNS OPT processing. The assessed vector is network-reachable with high attack complexity because the attacker generally needs to control or influence DNS responses (malicious authoritative server or on-path position) and the recursor must have ECS handling enabled. This is separate from the DNSSEC validation bypass and other issues in the same advisory.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
Remotely reachable without authentication (AV:N/PR:N), but AC:H because it only applies when ECS hardening is enabled and requires a specifically crafted OPT record; impact is a limited integrity/hardening bypass (I:L), no confidentiality or availability loss.
Description PRE-NVD
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
CVE.org
GitHub PoC
Exploit-DB