# cert-manager: Direct ACME Challenge resources can bypass Issuer DNS01 solver policy and use ClusterIssuer DNS credentials Advisory record · `GHSA-8rvj-mm4h-c258` - **Identifiers:** `GHSA-8rvj-mm4h-c258` · `BIT-cert-manager-2026-62290` · `CVE-2026-62290` · `GO-2026-6889` - **State:** Confirmed - **Severity:** CVSS 7.3 High - **Critical:** No - **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html) - **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md) - **Published:** 29 Oct 2026 - **Updated:** 5 Nov 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 29 Oct 2026, 16:39 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `github.com/cert-manager/cert-manager` (Go): affected `>=1.18.0, <1.19.6 || >=1.20.0-alpha.0, <1.20.3`; fixed in `1.19.6`, `1.20.3` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Affected: cert-manager versions 1.18.0 up to 1.19.6 and 1.20.0-alpha.0 up to 1.20.3. A namespace user who can create ACME Challenge resources can supply their own DNS01 solver configuration, so cert-manager uses ClusterIssuer DNS credentials outside the Issuer's solver policy. With acme-dns, the attacker-controlled host can receive the referenced account credentials. Upgrade to 1.19.6 or 1.20.3. 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.3 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0011, the 1st percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:11 UTC: First seen by agentprime - 31 Oct 2026, 14:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-8rvj-mm4h-c258) ## Sources - [GitHub Advisory Database: GHSA-8rvj-mm4h-c258](https://github.com/advisories/GHSA-8rvj-mm4h-c258) - [OSV: GHSA-8rvj-mm4h-c258](https://osv.dev/vulnerability/GHSA-8rvj-mm4h-c258) - - - - - - - - - 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 (), 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: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .