chore(deps): bump github.com/cert-manager/cert-manager from 1.20.2 to 1.20.3

[dependabot]

Bumps github.com/cert-manager/cert-manager from 1.20.2 to 1.20.3.

Release notes

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

v1.20.3

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

This patch release fixes a security issue (GHSA-8rvj-mm4h-c258, HIGH) where the default cert-manager-edit aggregate ClusterRole granted namespace users permission to create ACME Challenge and Order resources directly. A user who could create a Challenge referencing a ClusterIssuer could supply attacker-controlled solver configuration while cert-manager loaded credentials from the ClusterIssuer's namespace, bypassing Issuer solver selectors (dnsZones, dnsNames, matchLabels). With the acme-dns provider specifically, this could disclose DNS credentials to an attacker-controlled endpoint.

This release also removes the issuer owner reference from Challenges which was blocking Challenge garbage collection, and updates Go to fix reported CVEs.

All users should upgrade.

[!WARNING] Potentially breaking change: The cert-manager-edit aggregate ClusterRole no longer grants create for challenges.acme.cert-manager.io or create, patch, update for orders.acme.cert-manager.io. These resources are internal to cert-manager's ACME workflow and are not intended to be created or modified directly by users. If you have tooling or workflows that create Challenge or Order resources directly (outside of the normal Certificate → CertificateRequest → Order → Challenge flow), you will need to grant those permissions explicitly.

Changes by Kind

Bug or Regression

• Security (HIGH): Remove Challenge create and Order create, patch, update verbs from the cert-manager-edit aggregate ClusterRole (GHSA-8rvj-mm4h-c258). (#8940, @​wallrj-cyberark)
• Remove issuer owner reference from challenges blocking challenge garbage collection (#8759, @​cert-manager-bot)

Other (Cleanup or Flake)

• Bump go to 1.26.3, other deps to fix several govulncheck issues (#8789, @​SgtCoDFish)
• Update Go to v1.26.4 to fix CVE-2026-27145, CVE-2026-42504, and CVE-2026-42507 (#8926, @​wallrj-cyberark)

Commits

• 1e1d16d Merge pull request #8940 from wallrj-cyberark/restrict-edit-clusterrole-rbac-...
• 6bda472 Restrict Challenge and Order verbs in aggregate edit ClusterRole
• 3428d65 Merge pull request #8926 from wallrj-cyberark/update-go-1.26.4-release-1.20
• b352e55 [release-1.20] Update Go to v1.26.4
• 725a401 Merge pull request #8899 from cert-manager/renovate/release-1.20-base-images
• 29ae077 chore(deps): update base images
• 0bca8fd Merge pull request #8817 from cert-manager/renovate/release-1.20-go-golang.or...
• 15988af chore(deps): update module golang.org/x/net to v0.55.0 [security]
• 27414f9 Merge pull request #8818 from cert-manager/renovate/release-1.20-go-golang.or...
• 136b418 fix(deps): update module golang.org/x/crypto to v0.52.0 [security]
• Additional commits viewable in compare view

[vdemeester]

/retest

[jkhelil]

@dependabot rebase

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 25.55%. Comparing base (409a035) to head (39159ef).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3593   +/-   ##
=======================================
  Coverage   25.55%   25.55%           
=======================================
  Files         448      448           
  Lines       23317    23317           
=======================================
  Hits         5958     5958           
  Misses      16674    16674           
  Partials      685      685           

Flag	Coverage Δ
unit-tests	25.55% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jkhelil]

/approve

[jkhelil]

/lgtm

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jkhelil

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [jkhelil]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment