# CVE-2025-30195: A crafted zone can lead to an illegal memory access in the PowerDNS Recursor

> An attacker can cause a denial of service in PowerDNS Recursor by publishing a crafted zone that triggers an illegal memory access.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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:** 7 Apr 2025
- **Updated:** 7 Apr 2025
- **Also known as:** DEBIAN-CVE-2025-30195, GHSA-v9gv-mwp4-wx7g, UBUNTU-CVE-2025-30195

## What is CVE-2025-30195?

CVE-2025-30195 is a high-severity vulnerability in PowerDNS Recursor, published on 7 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An attacker can publish a zone containing specific Resource Record Sets. Processing and caching results for these sets can lead to an illegal memory accesses and crash of the Recursor, causing a denial of service.

The remedy is: upgrade to the patched 5.2.1 version.

We would like to thank Volodymyr Ilyin for bringing this issue to our attention.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2025-30195?


## How do I fix CVE-2025-30195?

Upgrade to a fixed version.

## Is CVE-2025-30195 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-30195 and fix it if it is affected.

What it is: CVE-2025-30195 is a high-severity vulnerability in PowerDNS Recursor, published on 7 Apr 2025. 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-2025-30195 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-2025-30195/ (Markdown: https://insights.sbomify.com/CVE-2025-30195/index.md)
```

## Sources

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

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