Skip to content

chore(deps): update dependency cert-manager/cert-manager to v1.19.4#651

Open
renovate[bot] wants to merge 2 commits intomainfrom
renovate/cert-manager-cert-manager-1.x
Open

chore(deps): update dependency cert-manager/cert-manager to v1.19.4#651
renovate[bot] wants to merge 2 commits intomainfrom
renovate/cert-manager-cert-manager-1.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 15, 2025

This PR contains the following updates:

Package Update Change
cert-manager/cert-manager patch 1.19.01.19.4

Release Notes

cert-manager/cert-manager (cert-manager/cert-manager)

v1.19.4

Compare Source

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

v1.19.4 is a simple patch release to fix some reported vulnerabilities - notably CVE-2026-24051 and CVE-2025-68121. All users should upgrade.

Changes by Kind

Bug or Regression

v1.19.3

Compare Source

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. (#​8415, @​cert-manager-bot)
  • Fixed an issue where HTTP-01 challenges failed when the Host header contained an IPv6 address. This means that users can now issue IP address certificates for IPv6 address subjects. (#​8436, @​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. (#​8468, @​SgtCoDFish)
Other (Cleanup or Flake)

v1.19.2

Compare Source

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.19 release notes on the cert-manager.io website before upgrading.

Changes since v1.19.1

Bug or Regression
  • Address false positive vulnerabilities CVE-2025-47914 and CVE-2025-58181 which were reported by Trivy. (#​8283, @​SgtCoDFish)
  • Update Go to v1.25.5 to fix CVE-2025-61727 and CVE-2025-61729 (#​8294, @​wallrj-cyberark)
  • Update global.nodeSelector to helm chart to perform a merge and allow for a single nodeSelector to be set across all services. (#​8233, @​cert-manager-bot)
Other (Cleanup or Flake)

v1.19.1

Compare Source

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

We reverted the CRD-based API defaults for Certificate.Spec.IssuerRef and CertificateRequest.Spec.IssuerRef after they were found to cause unexpected certificate renewals after upgrading to 1.19.0. We will try re-introducing these API defaults in cert-manager 1.20.
We fixed a bug that caused certificates to be re-issued unexpectedly if the issuerRef kind or group was changed to one of the "runtime" default values.
We upgraded Go to 1.25.3 to address the following security 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, and CVE-2025-61725.

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

Changes since v1.19.0:

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 (#​8175, @​cert-manager-bot)
  • Bump Go to 1.25.3 to fix a backwards incompatible change to the validation of DNS names in X.509 SAN fields which prevented the use of DNS names with a trailing dot (#​8177, @​wallrj-cyberark)
  • Revert API defaults for issuer reference kind and group introduced in 0.19.0 (#​8178, @​cert-manager-bot)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependency Dependency version related label Oct 15, 2025
@renovate renovate bot force-pushed the renovate/cert-manager-cert-manager-1.x branch from 8c97a3c to 3398a6f Compare October 22, 2025 14:51
@renovate renovate bot force-pushed the renovate/cert-manager-cert-manager-1.x branch from 4ab078b to 4a7ceeb Compare November 10, 2025 23:40
@renovate renovate bot changed the title chore(deps): update dependency cert-manager/cert-manager to v1.19.1 chore(deps): update dependency cert-manager/cert-manager to v1.19.2 Dec 9, 2025
@renovate renovate bot force-pushed the renovate/cert-manager-cert-manager-1.x branch 2 times, most recently from c2f5c9d to 809f3d4 Compare December 10, 2025 15:42
@renovate renovate bot force-pushed the renovate/cert-manager-cert-manager-1.x branch from aad0501 to 52b85cb Compare February 2, 2026 21:01
@renovate renovate bot changed the title chore(deps): update dependency cert-manager/cert-manager to v1.19.2 chore(deps): update dependency cert-manager/cert-manager to v1.19.3 Feb 2, 2026
@renovate renovate bot changed the title chore(deps): update dependency cert-manager/cert-manager to v1.19.3 chore(deps): update dependency cert-manager/cert-manager to v1.19.4 Feb 24, 2026
@renovate renovate bot force-pushed the renovate/cert-manager-cert-manager-1.x branch from 52b85cb to b9292a8 Compare February 24, 2026 17:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependency Dependency version related

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant