# CVE-2026-40011: Prometheus denial of service via crafted DNS queries

> Attackers can cause denial of service in Prometheus monitoring by sending crafted DNS queries to PowerDNS DNSdist, blocking valid scrapes.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-40011, GHSA-f83r-q8f4-f336, UBUNTU-CVE-2026-40011

## What is CVE-2026-40011?

CVE-2026-40011 is a low-severity denial of service vulnerability in PowerDNS DNSdist, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An attacker sending a large number of crafted DNS queries might be able to trigger a dynamic block being inserted with a value causing invalid output to be produced in the prometheus endpoint. The prometheus endpoint will then be rejected by the scraper until the dynamic block expires.

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

## Which versions are affected by CVE-2026-40011?


## How do I fix CVE-2026-40011?

Upgrade to a fixed version.

## Is CVE-2026-40011 being exploited?

There is no known exploitation of CVE-2026-40011 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-40011 and fix it if it is affected.

What it is: CVE-2026-40011 is a low-severity denial of service vulnerability in PowerDNS DNSdist, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-40011 in the wild and no public exploit code.

Affected product: PowerDNS DNSdist. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-40011/ (Markdown: https://insights.sbomify.com/CVE-2026-40011/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40011
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40011
- OSV: https://osv.dev/vulnerability/CVE-2026-40011

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-40011/
Summaries are generated and may contain mistakes; the official description above is the record.