# CVE-2026-62290: cert-manager: Direct ACME Challenge resources can bypass Issuer DNS01 solver policy and use ClusterIssuer DNS credentials

> Namespace users can bypass DNS01 solver policies to use ClusterIssuer credentials, potentially disclosing sensitive API keys.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jul 2026
- **Updated:** 18 Jul 2026
- **Also known as:** BIT-cert-manager-2026-62290, GHSA-8rvj-mm4h-c258, MINI-4v29-w8ch-j6pp, MINI-7797-hgj8-qvpj, MINI-78rj-fc3c-2mcj, MINI-g2h4-6qcj-r62h

## What is CVE-2026-62290?

CVE-2026-62290 is a high-severity missing authorization vulnerability in cert-manager, published on 16 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

cert-manager adds certificates and certificate issuers as resource types in Kubernetes clusters, and simplifies the process of obtaining, renewing and using those certificates. From 1.18.0 until 1.19.6 and 1.20.3, Challenge resources under acme.cert-manager.io can be created directly by namespace users without admission validation tying the Challenge to an Order, owner reference, or Issuer-selected solver, allowing attacker-controlled Challenge.spec.solver values referencing a ClusterIssuer to bypass DNS01 solver selectors such as dnsZones, dnsNames, and matchLabels and cause cert-manager to use ClusterIssuer DNS credentials for attacker-selected provider settings and DNS names, including disclosure of X-Api-User and X-Api-Key headers for acme-dns. This issue is fixed in versions 1.19.6 and 1.20.3.

Weakness: CWE-863 (Incorrect Authorization)

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

5 open source packages ship an affected version, including github.com/cert-manager/cert-manager and cert-manager. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/cert-manager/cert-manager` | Go | From 1.18.0 | 1.19.6 |
| `github.com/cert-manager/cert-manager` | Go | From 1.18.0 | 1.19.6 |
| `github.com/cert-manager/cert-manager` | Go | From 1.20.0-alpha.0 | 1.20.3 |
| `github.com/cert-manager/cert-manager` | Go | From 1.20.0-alpha.0 | 1.20.3 |
| `cert-manager` | Bitnami | From 1.18.0 | 1.19.6, 1.20.3 |

Products: Linuxfoundation Cert-Manager.

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

Upgrade github.com/cert-manager/cert-manager to a fixed version for your release line: 1.19.6 or 1.20.3.

## Is CVE-2026-62290 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-62290 is a high-severity missing authorization vulnerability in cert-manager, published on 16 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-62290 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/cert-manager/cert-manager (Go): affected from 1.18.0; fixed in 1.19.6
- github.com/cert-manager/cert-manager (Go): affected from 1.18.0; fixed in 1.19.6
- github.com/cert-manager/cert-manager (Go): affected from 1.20.0-alpha.0; fixed in 1.20.3
- github.com/cert-manager/cert-manager (Go): affected from 1.20.0-alpha.0; fixed in 1.20.3
- cert-manager (Bitnami): affected from 1.18.0; fixed in 1.19.6, 1.20.3

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-62290/ (Markdown: https://insights.sbomify.com/CVE-2026-62290/index.md)
```

## Sources

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

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