# CoreDNS: DNS Cache Pinning via etcd Lease ID Confusion

Advisory record · `GHSA-93mf-426m-g6x9`

- **Identifiers:** `GHSA-93mf-426m-g6x9` · `CVE-2025-58063` · `GO-2025-3942`
- **State:** Confirmed
- **Severity:** CVSS 7.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-681](https://cwe.mitre.org/data/definitions/681.html)
- **Tags:** [CWE-681](https://agentprime.io/advisories/tag/cwe-681.md)
- **Published:** 9 Sept 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 9 Sept 2025, 19:19 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/coredns/coredns` (Go): affected `>=1.2.0, <1.12.4`; fixed in `1.12.4`

## Machine-written summary

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

> CoreDNS versions 1.2.0 up to but not including 1.12.4 use the etcd plugin in a way that treats etcd lease IDs as TTL values, so records can receive very long TTLs. An attacker with write access to etcd can attach a lease to a record, causing downstream resolvers and clients to cache answers for a very long time, which can delay changes to services. Upgrade to CoreDNS 1.12.4 or later.

Written 1 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

- 7.1 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0051, the 43rd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:14 UTC: First seen by agentprime
- 31 Oct 2026, 14:14 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-93mf-426m-g6x9)

## Sources

- [GitHub Advisory Database: GHSA-93mf-426m-g6x9](https://github.com/advisories/GHSA-93mf-426m-g6x9)
- [OSV: GHSA-93mf-426m-g6x9](https://osv.dev/vulnerability/GHSA-93mf-426m-g6x9)
- <https://github.com/coredns/coredns/security/advisories/GHSA-93mf-426m-g6x9>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-58063>
- <https://github.com/coredns/coredns/commit/e1768a5d272e9da649dfb8588595e5c6e4e640bf>
- <https://github.com/coredns/coredns>

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-93mf-426m-g6x9>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-93mf-426m-g6x9/>. Everything for agents: <https://agentprime.io/llms.txt>.