External risk intelligence

Attacker can take control of dnsdist or disrupt service via crafted responses.

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-33598

A critical flaw in PowerDNS dnsdist could let an attacker crash your service or access sensitive data using specially crafted DNS responses, especially if you use custom scripting.

5Halo Surface Signal

Out-of-bounds Read

Powerdns Dnsdist

1.9.0 to before 1.9.132.0.0 to before 2.0.4

External exposure likelihood

Halo Surface Signal score for CVE-2026-33598

dnsdist is a DNS load balancer and security component designed to sit at the network edge, handling external DNS requests. These services are commonly deployed to face the internet or broad network segments to manage traffic flows, making them inherently accessible from the network perimeter.

Horizon Alert

Summary of the vulnerability and why it matters

This issue in dnsdist could allow an attacker to cause denial of service or potentially access sensitive information. It occurs when custom code processes a specially crafted cached response, leading to an out-of-bounds read.

  • This impacts systems handling DNS traffic.
  • It can lead to crashes or data leaks.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker could exploit this vulnerability by sending crafted DNS requests that result in a malicious, out-of-bounds read in the packet cache. If custom Lua code is used to process cached responses, this read could lead to denial-of-service by crashing the server or potentially allow for information disclosure if the read accesses sensitive memory.

  • Network access is required.
  • Vulnerable to crafted DNS responses.
  • Lua scripting must be enabled.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability allows for an out-of-bounds read when custom Lua code interacts with cached DNS responses. Because the affected component, dnsdist, often operates at the network edge, it is frequently exposed to external, unauthenticated network traffic, making it a prime target for attackers. While there are no immediate indicators of active exploitation, the critical nature and network exposure suggest a high likelihood of weaponization.

  • Exposed perimeter service.
  • No known exploit in the wild.
  • Recently disclosed.

Priority actions

Operational Fix

Recommended remediation, mitigation, and detection steps

Prioritize isolating or taking offline PowerDNS dnsdist instances using custom Lua code that calls `getDomainListByAddress()` or `getAddressListByDomain()` on packet caches. This vulnerability, rated critical, allows for an out-of-bounds read via a crafted response.

  • Update dnsdist to 1.9.13 or 2.0.4.
  • Monitor network traffic for unusual DNS responses.
  • Temporarily disable Lua features if patching is delayed.

Frequently asked questions

What is PowerDNS dnsdist?

PowerDNS dnsdist is a DNS load balancer and performance enhancement tool. It is used to distribute DNS traffic across multiple DNS servers, improving reliability and speed for DNS resolution services.

What is CVE-2026-33598 and what weakness does it represent?

CVE-2026-33598 is a critical vulnerability in PowerDNS dnsdist. It is an out-of-bounds read weakness (CWE-125) that can occur when custom Lua code processes a malformed cached DNS response.

How could an attacker trigger this vulnerability?

An attacker could trigger this by sending specially crafted DNS requests. This vulnerability is not triggered if custom Lua code is not in use or if the specific functions `getDomainListByAddress()` or `getAddressListByDomain()` are not called on a packet cache.

Who should care about this vulnerability given its exposure?

Organizations running PowerDNS dnsdist, especially those with it deployed as an internet-facing service (very likely exposure), should care. This is because it handles external DNS requests and is accessible from the network perimeter.

What are the first steps for running this technology?

As a first step, consider updating PowerDNS dnsdist to version 1.9.13 or 2.0.4. If immediate patching isn't possible, temporarily disable Lua features that call the affected functions on packet caches.

References