Quick answers
- Is CVE-2026-24029 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-24029 being exploited in the wild.
- How severe is CVE-2026-24029?
- Medium severity, with a CVSS score of 6.5, published 31 March 2026.
- Which products and versions are affected?
- Powerdns Dnsdist 1.9.0 to 1.9.11, 2.0.0 to 2.0.2.
- Is there a fix for CVE-2026-24029?
- A patch was published on 2026-03-31: Fixed versions 1.9.12 and 2.0.3 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-24029 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-24029?
- Check whether you run Powerdns Dnsdist at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An incorrect authorization vulnerability (CWE-863) exists in PowerDNS DNSdist when using the nghttp2 provider for DNS over HTTPS (DoH) frontends. If the 'early_acl_drop' (earlyACLDrop in Lua) configuration option is explicitly disabled (it is enabled by default), the engine skips the ACL check entirely. This allows any remote client to successfully send DoH queries regardless of the configured access restrictions. The vulnerability affects versions 1.9.0 through 1.9.11 and 2.0.0 through 2.0.2. A fix is available in versions 1.9.12 and 2.0.3.
Affected products
- PowerDNS DNSdist 1.9.0 to 1.9.11, 2.0.0 to 2.0.2
Timeline
- 2026-02-12: disclosed: Discovery date
- 2026-03-31: advisory: Vendor advisory published
- 2026-03-31: patched: Fixed versions 1.9.12 and 2.0.3 released