build(deps): Bump github.com/cert-manager/cert-manager from 1.18.2 to 1.18.5

[dependabot]

Bumps github.com/cert-manager/cert-manager from 1.18.2 to 1.18.5.

Release notes

Sourced from github.com/cert-manager/cert-manager's releases.

v1.18.5

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

This release contains three bug fixes, including a fix for the MODERATE severity DoS issue in GHSA-gx3x-vq4p-mhhv. All users should upgrade to the latest release.

Changes by Kind

Bug or Regression

• Fixed an infinite re-issuance loop that could occur when an issuer returns a certificate with a public key that doesn't match the CSR. The issuing controller now validates the certificate before storing it and fails with backoff on mismatch. (#8414, @​cert-manager-bot)
• Fixed an issue where HTTP-01 challenges failed when the Host header contains an IPv6 address. This means that users can now issue IP address certificates for IPv6 address subjects. (#8437, @​cert-manager-bot)
• Security (MODERATE): Fix a potential panic in the cert-manager controller when a DNS response in an unexpected order was cached. If an attacker was able to modify DNS responses (or if they controlled the DNS server) it was possible to cause denial of service for the cert-manager controller. (#8467, @​SgtCoDFish)

Other (Cleanup or Flake)

• Bump go to 1.24.12 (#8460, @​SgtCoDFish)

v1.18.4

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

We updated Go to fix some vulnerabilities in the standard library.

📖 Read the full 1.18 release notes on the cert-manager.io website before upgrading.

Changes since v1.18.3

Bug or Regression

• Address false positive vulnerabilities CVE-2025-47914 and CVE-2025-58181 which were reported by Trivy. (#8282, @​SgtCoDFish)
• Update Go to v1.24.11 to fix CVE-2025-61727 and CVE-2025-61729 (#8295, @​wallrj-cyberark)

Other (Cleanup or Flake)

• Update cert-manager's ACME client, forked from golang/x/crypto (#8271, @​SgtCoDFish)
• Updated Debian 12 distroless base images (#8328, @​wallrj-cyberark)

v1.18.3

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

We fixed a bug which caused certificates to be re-issued unexpectedly, if the issuerRef kind or group was changed to one of the "runtime" default values. We increased the size limit when parsing PEM certificate chains to handle leaf certificates with large numbers of DNS named or other identities. We upgraded Go to 1.24.9 to fix various non-critical security vulnerabilities.

📖 Read the full 1.18 release notes on the cert-manager.io website before upgrading.

Changes since v1.18.2:

Bug or Regression

• BUGFIX: in case kind or group in the issuerRef of a Certificate was omitted, upgrading to 1.19.x incorrectly caused the certificate to be renewed (#8174, @​cert-manager-bot)
• Bump Go to 1.24.9. Fixes the following vulnerabilities: CVE-2025-61724, CVE-2025-58187, CVE-2025-47912, CVE-2025-58183, CVE-2025-61723, CVE-2025-58186, CVE-2025-58185, CVE-2025-58188, CVE-2025-61725 (#8176, @​wallrj-cyberark)

... (truncated)

Commits

• 9a73a0b Merge pull request #8467 from SgtCoDFish/release-1.18-fqdn-patch
• 2401487 [release-1.18] security: address GHSA-gx3x-vq4p-mhhv
• 31a995e Merge pull request #8460 from SgtCoDFish/release-1.18-bumpgo
• 528113d [release-1.18] bump base images using hack/latest-base-images.sh
• 89c1781 [release-1.18] bump go to latest 1.24 release
• 5a6ef3d Merge pull request #8437 from cert-manager-bot/cherry-pick-8424-to-release-1.18
• ba0117b fix(HTTP-01): handling of IPv6 address literals
• d8fda9c Merge pull request #8414 from cert-manager-bot/cherry-pick-8403-to-release-1.18
• 58bd9f6 Fail issuance when certificate public key doesn't match CSR
• 8d5d2e4 Fail issuance when certificate public key doesn't match CSR (#8380)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

• title ~= ^(\[wip\]|\[backport\]|\[cherry-pick\])?( )?(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?:

🟢 Enforce verified commits

Wonderful, this rule succeeded.

Make sure that we have verified commits

• #commits-unverified = 0

🟢 Enforce linear history

Wonderful, this rule succeeded.

Make sure that we have a linear history, no merge commits are allowed

• linear-history