Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach Recursor webserver endpoint
-
ExploitOpen TLS connection without completing handshake
-
ExecutionWeb handler blocks on stalled client
-
ImpactLegitimate web/API access denied
Vulnerability Assessment
| Exploitation Conditions | Requires network reachability to the PowerDNS Recursor built-in webserver/REST API (the TLS/HTTPS-enabled web endpoint); exploitation consists of initiating but never completing a TLS handshake to that service, monopolizing the single web handler. Limiting factors: the Recursor webserver is disabled or bound to 127.0.0.1 by default and is normally restricted to trusted management networks, so an attacker must have access to the administrative interface; impact is confined to the web/API interface and does not interrupt DNS resolution, cache integrity, or DNSSEC validation. No authentication appears necessary to begin the TLS handshake, but authentication requirements are not confirmed from available data since no CVSS vector was published. |
| Impact | No CVSS vector, EPSS score, KEV listing, or POC is provided for CVE-2026-85557, so this assessment relies on the vendor advisory text alone. PowerDNS Security Advisory 2026-12 explicitly states that three of its CVEs are rated High and the remainder (which includes this one) are Medium or Low; this issue - 'Single web client not doing TLS handshake monopolizes web access' - is a resource-monopolization denial-of-service affecting only the Recursor's built-in webserver/API, not the core DNS resolution path. The real-world priority is modest: it does not compromise confidentiality or integrity, does not poison the cache, and does not affect DNS answers served to clients. The practical risk is further bounded by the fact that the PowerDNS Recursor webserver binds to 127.0.0.1 by default and is typically restricted to trusted management networks, so an attacker needs reachability to that administrative interface. There is no evidence of active exploitation and no public exploit code identified. Net: a legitimate availability bug worth patching during normal maintenance, not an emergency - closer to a 'medium/low severity, low real-world risk' issue than a high-priority threat. Note the absence of a vendor-published CVSS vector means attack-vector and privilege details below are inferred from the advisory title and PowerDNS defaults, not confirmed by NVD. |
| Exploit ScenarioDerived | An attacker able to reach the Recursor's HTTPS webserver/API endpoint opens a TLS connection but deliberately never completes the handshake, holding the single-threaded web handler and blocking all other administrators and monitoring tools from accessing the web interface or API. No public exploit code is identified, but the technique is a well-understood slow-handshake/slowloris pattern requiring only a single stalled connection. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
PowerDNS Recursor releases before 5.3.12 and 5.4.8 can be tied up by a client that opens a connection to the built-in web server/REST API and never completes the TLS handshake, leaving the single web handler occupied and denying web/API access to legitimate users. The flaw is one of seven issues fixed in PowerDNS Security Advisory 2026-12 (tracked as CVE-2026-85557) and only matters where the web server is enabled and reachable, since it is disabled or bound to loopback by default; DNS resolution, cache integrity and DNSSEC validation are unaffected. No public exploit code, EPSS score or CISA KEV listing was provided, and no vendor CVSS vector accompanies this specific CVE, so the recorded impact is limited to availability of the web interface (assessed CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).
RemediationAI
Vendor-released patch: upgrade to PowerDNS Recursor 5.4.8 or 5.3.12 (both released 21 October 2026; tarballs and detached signatures are on https://downloads.powerdns.com/releases/ and distribution packages on https://repo.powerdns.com/). Because the advisory bundles seven CVEs of High, Medium and Low severity-including the DNSSEC validation bypass and cache-poisoning issue CVE-2026-85555 and the out-of-bounds read CVE-2026-85559-treat the upgrade as mandatory rather than deferrable for any internet-facing resolver. If upgrading immediately is impossible, the decisive compensating control is to eliminate reachability of the web service: disable it entirely with webserver=no (side effect: loss of the REST API, statistics endpoints and API-driven cache/RPZ operations, so dashboards and automation must be paused), or keep it enabled but bind it to loopback with webserver-address=127.0.0.1 and restrict clients via webserver-allow-from plus a host firewall or management-network ACL (side effect: remote administration must go through an SSH tunnel or jump host). Terminating TLS in front of the API on a reverse proxy with handshake timeouts and per-client connection limits also shrinks the window, but it adds a component to maintain and must not re-expose the plaintext listener. Detection can be approximated by watching for long-lived, incomplete TLS connections to the web port and by alerting on saturation of the web handler; none of these workarounds fix the underlying single-handler design, so the patched release remains the only complete remedy. Consult https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2026-12.html and the changelogs for the exact per-CVE details before scheduling the change window.
Affected ProductsAI
PowerDNS Recursor release trains prior to the October 2026 security releases are affected: the 5.4.x train up to and including 5.4.7 and the 5.3.x train up to and including 5.3.11, with fixes shipped in 5.4.8 and 5.3.12 (released 21 October 2026, pull requests 18197 and 18198 respectively). Exposure is limited to deployments that enable the Recursor web server/REST API and allow it to be reached from untrusted networks-the default configuration disables it or binds it to 127.0.0.1. No CPE identifiers were provided in the source data, so version matching should be done against the vendor changelogs at https://doc.powerdns.com/recursor/changelog/5.4.html#change-5.4.8 and https://doc.powerdns.com/recursor/changelog/5.3.html#change-5.3.12, and the consolidated advisory at https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2026-12.html. Note that 5.3.13 (same day) only fixes a performance regression from SA-2026-08 affecting scope-zero ECS answers; it is not required for this CVE. Organisations running EOL trains should also check the revised support policy at https://docs.powerdns.com/recursor/appendices/EOL.html.
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
The PowerDNS Recursor ships an optional embedded web server that also exposes a REST API for statistics, configuration and control (for example flushing caches and manipulating RPZ/NTA state). That service can be configured with TLS (webserver-password plus the webserver TLS/HTTPS settings) and handles requests through a single handler, so a connection that stalls mid-handshake-TCP accepted, ClientHello sent or withheld, handshake never finished-consumes the handler's attention and blocks subsequent, legitimate management requests. This is a classic asymmetric resource-consumption pattern: the attacker spends a cheap half-open TLS session while the victim loses a scarce, non-scalable service slot. No CWE identifier was supplied with the CVE; the behaviour aligns with the uncontrolled-resource-consumption / allocation-without-limits class (CWE-400/CWE-770) applied to a connection handler rather than to a buffer or parser. Scope is important here: the same advisory (SA-2026-12) bundles unrelated memory-safety and protocol-logic defects (decompression DoS, TIME_WAIT exhaustion, DNSSEC validation bypass and cache poisoning, missing OPT RR owner-name validation defeating ECS hardening, unbounded retention of closed TCP client addresses, out-of-bounds read in findScopeZero), and those carry different preconditions and severities than this web-handler issue-they should be assessed and prioritised separately.
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
A stalled TLS handshake needs no auth or interaction (PR:N/UI:N/AC:L) and reaches the network-exposed webserver (AV:N); impact is limited to availability of the management interface only, so C:N/I:N/A:L.
Description PRE-NVD
Executive ViewAI
PowerDNS Recursor's built-in web server/REST API can be tied up by an unauthenticated client that leaves a TLS handshake incomplete, denying management/API access to legitimate users on instances where that interface is enabled and reachable; DNS resolution, cache integrity, and DNSSEC validation are unaffected, and the interface is disabled or loopback-bound by default. Leadership should care because this is a limited availability issue for administrative tooling rather than core DNS service, but exposed management interfaces could disrupt operational workflows; no public exploit was identified at time of analysis.
No vendor-released patch identified at time of analysis; interim mitigations include disabling the built-in web server/REST API where not needed, binding it to loopback, restricting access to trusted management networks via firewall/ACL, and monitoring for stalled TLS handshakes. If the advisory's fixed releases 5.3.12 or 5.4.8 are available, apply vendor patch.
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