cve.bz

CVE-2026-40208 powerdns dnsdist: Incorrect Control Flow Scoping

3.7 lowEPSS 0.4%

Low (3.7) in powerdns dnsdist. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
An attacker might be able to delay the processing of DoH3 queries by sending DoH3 GET queries with an invalid DATA frame.

Severity

CVSS 3.1

3.7 low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 35th percentile. Scored 2026-11-15. 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-06-25. 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-705 Incorrect Control Flow Scoping
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-40208 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-40208?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-40208?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-40208 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.

Badge for a README or a site

CVE-2026-40208

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-40208](https://cve.bz/cve/badge/CVE-2026-40208.svg)](https://cve.bz/cve/CVE-2026-40208)

HTML:

<a href="https://cve.bz/cve/CVE-2026-40208"><img src="https://cve.bz/cve/badge/CVE-2026-40208.svg" alt="CVE-2026-40208"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
PowerDNS DNSdistfrom 1.9.0 before 1.9.15
PowerDNS DNSdistfrom 2.0.0 before 2.0.7

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12dnsdistno fix listedDEBIAN-CVE-2026-40208
Debian13dnsdist1.9.15-0+deb13u1DEBIAN-CVE-2026-40208
Debian14dnsdist2.1.0-1DEBIAN-CVE-2026-40208
Ubuntu16.04:LTS, 25.10, 26.04:LTS and 5 morednsdistno fix listedUBUNTU-CVE-2026-40208
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0dnsdist1.9.15-160000.1.1SUSE-SU-2026:23123-1 SUSE-SU-2026:23146-1
openSUSELeap 16.0dnsdist1.9.15-160000.1.1openSUSE-SU-2026:21533-1
openSUSETumbleweeddnsdist2.0.7-1.1openSUSE-SU-2026:11411-1

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. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.

References

Check your stackJSON