# Hickory DNS's DNSSEC validation may accept broken authentication chains

Advisory record · `GHSA-37wc-h8xc-5hc4`

- **Identifiers:** `GHSA-37wc-h8xc-5hc4` · `CVE-2025-25188`
- **State:** Confirmed
- **Severity:** CVSS 5.7 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-345](https://cwe.mitre.org/data/definitions/345.html)
- **Tags:** [CWE-345](https://agentprime.io/advisories/tag/cwe-345.md)
- **Published:** 10 Feb 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 10 Feb 2025, 17:46 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `hickory-proto` (crates.io): affected `>=0.8.0, <0.24.3`; fixed in `0.24.3`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Hickory DNS's \`hickory-proto\` crate, versions 0.8.0 up to but not including 0.24.3, may accept DNSKEY records as trusted for DNSSEC validation when only one key in the set matches a trust anchor or is covered by a DS record, so other unauthenticated keys in the zone are wrongly trusted. The source does not describe the attacker's position or required access. Upgrade to hickory-proto 0.24.3 or later.

Written 8 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.7 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0028, the 20th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:17 UTC: First seen by agentprime
- 31 Oct 2026, 15:17 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-37wc-h8xc-5hc4)

## Sources

- [GitHub Advisory Database: GHSA-37wc-h8xc-5hc4](https://github.com/advisories/GHSA-37wc-h8xc-5hc4)
- [OSV: GHSA-37wc-h8xc-5hc4](https://osv.dev/vulnerability/GHSA-37wc-h8xc-5hc4)
- <https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-37wc-h8xc-5hc4>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-25188>
- <https://github.com/hickory-dns/hickory-dns/commit/e118c6eec569f4340421f86ee0686714010c63e9>
- <https://github.com/hickory-dns/hickory-dns>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-37wc-h8xc-5hc4>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-37wc-h8xc-5hc4/>. Everything for agents: <https://agentprime.io/llms.txt>.