# cert-manager v1.18.4

2025-12-09 · [Original release notes](https://github.com/cert-manager/cert-manager/releases/tag/v1.18.4) · [Full summary](https://ratatosk.io/en/releases/cert-manager/v1.18.4)

Security 2 · Breaking changes 2 · Dependency updates 2

## Check before upgrading

### Upgrade guide

- **Full 1.18 release notes**
  > > 📖 Read the [full 1.18 release notes](https://cert-manager.io/docs/releases/release-notes/release-notes-1.18) on the cert-manager.io website before upgrading.

## Security (2)

### Go `crypto/x509` certificate verification flaws fixed

- Affects: host-certificate verification by cert-manager components built with affected Go versions (Inferred)
- [CVE-2025-61727](https://www.cve.org/CVERecord?id=CVE-2025-61727), [CVE-2025-61729](https://www.cve.org/CVERecord?id=CVE-2025-61729)

A wildcard SAN could claim a subdomain excluded by a certificate-chain constraint; formatting a `HostnameError` for a certificate with many hosts could consume excessive resources. The release updates Go to v1.24.11 to fix the two listed CVEs.

> - Update Go to v1.24.11 to fix CVE-2025-61727 and CVE-2025-61729 ( #8295 , @wallrj-cyberark )
> We updated Go to fix some vulnerabilities in the standard library.
> - Update Go to `v1.24.11` to fix `CVE-2025-61727` and `CVE-2025-61729` (#8295, @wallrj-cyberark)
> We updated Go to fix some vulnerabilities in the Go standard library.

https://cert-manager.io/docs/releases/release-notes/release-notes-1.18

### Legacy ACME TLS-SNI challenge certificate generation disabled

- Affects: ACME TLS-SNI-01 or TLS-SNI-02 challenge handling (Inferred)

Previously, `TLSSNI01ChallengeCert` and `TLSSNI02ChallengeCert` generated and returned challenge certificates. Now, calls to either method return an error without a certificate or name.

> - Update cert-manager's ACME client, forked from `golang/x/crypto` (#8271, @SgtCoDFish)

## Breaking changes (2)

### TLS-ALPN-01 certificates use IP address SANs for IP identifiers

- Affects: TLS-ALPN-01 validation for IP address identifiers

For domain identifiers, the generated certificate carries a DNS SAN and subject common name.

Evidence: “+// Validation requests for IP address identifiers will use the reverse DNS form in the server name” https://github.com/cert-manager/cert-manager/pull/8271

> - Update cert-manager's ACME client, forked from `golang/x/crypto` (#8271, @SgtCoDFish)
> - Update cert-manager's ACME client, forked from golang/x/crypto ( #8271 , @SgtCoDFish )

### ACME nonce-fetching requests now use the supplied context

- Affects: ACME nonce requests made through this client (Inferred)

Previously, the nonce-fetching `HEAD` request was created without the supplied context.

> - Update cert-manager's ACME client, forked from `golang/x/crypto` (#8271, @SgtCoDFish)

## Dependency updates (2)

### Updated `golang.org/x/crypto` dependency

- [CVE-2025-47914](https://www.cve.org/CVERecord?id=CVE-2025-47914), [CVE-2025-58181](https://www.cve.org/CVERecord?id=CVE-2025-58181)

The dependency moved from `v0.38.0` to `v0.45.0` to address Trivy reports that the pull request identified as false positives for cert-manager.

> - Address false positive vulnerabilities CVE-2025-47914 and CVE-2025-58181 which were reported by Trivy. ( #8282 , @SgtCoDFish )
> - Address false positive vulnerabilities `CVE-2025-47914` and `CVE-2025-58181` which were reported by Trivy. (#8282, @SgtCoDFish)

https://cert-manager.io/docs/releases/release-notes/release-notes-1.18

1 more, none mentioning security

- `- Updated Debian 12 distroless base images ( #8328 , @wallrj-cyberark )`

---

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.
