# CVE-2026-52690: Spoofed answers can mark an authoritative non-EDNS capable

> Attackers can spoof replies to mark authoritative servers as non-EDNS capable, causing DNSSEC validation failures in PowerDNS Recursor.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **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-52690, GHSA-c2h5-7f6m-jqmp, UBUNTU-CVE-2026-52690

## What is CVE-2026-52690?

CVE-2026-52690 is a medium-severity vulnerability in PowerDNS Recursor, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Spoofing replies to Recursor might mark an IP of an authoritative server as not supporting EDNS, causing valdiation of DNSSEC records served by that server to fail.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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


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

Apply the vendor's patch.

## Is CVE-2026-52690 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-52690 is a medium-severity vulnerability in PowerDNS Recursor, 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-52690 in the wild and no public exploit code.

Affected product: PowerDNS Recursor. 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-52690/ (Markdown: https://insights.sbomify.com/CVE-2026-52690/index.md)
```

## Sources

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

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