OCPBUGS-98108,OCPBUGS-95492: Bump golang.org/x/crypto to fix CVE-2025-22869,CVE-2025-47913,CVE-2026-46597,CVE-2026-39829,CVE-2026-39832 by redhat-chai-bot · Pull Request #550 · openshift/builder

redhat-chai-bot · 2026-09-01T07:43:46Z

Summary

Bumps golang.org/x/crypto using the openshift-sustaining/crypto security fork (version v0.33.0-sec.5) to address multiple crypto CVEs.

Fork version selected based on Go minimum version 1.22.8 (Go >= 1.20, < 1.23 range).

CVEs Fixed

Jira Trackers

AI-generated. Review for accuracy.

@prabhapa requested in Slack thread

…-22869,CVE-2025-47913,CVE-2026-46597,CVE-2026-39829,CVE-2026-39832

coderabbitai · 2026-09-01T07:43:53Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: 72cb75cd-bdd9-45eb-9dbd-d1bcc9211904

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

_{Comment @coderabbitai help to get the list of available commands.}

openshift-ci-robot · 2026-09-01T07:43:59Z

@redhat-chai-bot: This pull request references Jira Issue OCPBUGS-98108, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected Jira Issue OCPBUGS-98108 to depend on a bug targeting a version in 5.1.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-95492, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected Jira Issue OCPBUGS-95492 to depend on a bug targeting a version in 5.1.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

Bumps golang.org/x/crypto using the openshift-sustaining/crypto security fork (version v0.33.0-sec.5) to address multiple crypto CVEs.

Fork version selected based on Go minimum version 1.22.8 (Go >= 1.20, < 1.23 range).

CVEs Fixed

CVE-2025-22869

CVE-2025-47913

CVE-2026-46597

CVE-2026-39829

CVE-2026-39832

Jira Trackers

OCPBUGS-98108

OCPBUGS-95492

AI-generated. Review for accuracy.

@prabhapa requested in Slack thread

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-merge-bot · 2026-09-01T07:44:09Z

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

prabhapa · 2026-09-01T09:17:57Z

/pipeline required

openshift-merge-bot · 2026-09-01T09:18:01Z

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-ovn
/test e2e-aws-ovn-builds
/test e2e-aws-ovn-image-ecosystem

prabhapa · 2026-09-02T05:44:47Z

/retest

prabhapa · 2026-09-02T14:26:37Z

/label backport-risk-assessed

moebasim · 2026-09-02T14:46:42Z

/lgtm

moebasim · 2026-09-02T14:48:08Z

/jira refresh

openshift-ci-robot · 2026-09-02T14:48:13Z

@moebasim: This pull request references Jira Issue OCPBUGS-98108, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected Jira Issue OCPBUGS-98108 to depend on a bug targeting a version in 5.1.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

This pull request references Jira Issue OCPBUGS-95492, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected Jira Issue OCPBUGS-95492 to depend on a bug targeting a version in 5.1.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-merge-bot · 2026-09-02T14:48:46Z

Tests from second stage were triggered manually. Pipeline can be controlled only manually, until HEAD changes. Use command to trigger second stage.

openshift-ci · 2026-09-02T14:48:53Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: moebasim, redhat-chai-bot

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~~ [moebasim]

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

prabhapa · 2026-09-03T06:49:46Z

/verified by CI

openshift-ci-robot · 2026-09-03T06:50:00Z

@prabhapa: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

prabhapa · 2026-09-03T09:53:07Z

/jira refresh

openshift-ci-robot · 2026-09-03T09:53:12Z

@prabhapa: This pull request references Jira Issue OCPBUGS-98108, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected Jira Issue OCPBUGS-98108 to depend on a bug targeting a version in 5.1.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

This pull request references Jira Issue OCPBUGS-95492, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected Jira Issue OCPBUGS-95492 to depend on a bug targeting a version in 5.1.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

prabhapa · 2026-09-09T13:14:18Z

/retest

prabhapa · 2026-09-10T05:03:45Z

/label jira/skip-dependent-bug-check
main branch is already fixed

openshift-ci-robot · 2026-09-10T05:04:12Z

@redhat-chai-bot: This pull request references Jira Issue OCPBUGS-98108, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

This pull request references Jira Issue OCPBUGS-95492, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Summary

Bumps golang.org/x/crypto using the openshift-sustaining/crypto security fork (version v0.33.0-sec.5) to address multiple crypto CVEs.

Fork version selected based on Go minimum version 1.22.8 (Go >= 1.20, < 1.23 range).

CVEs Fixed

CVE-2025-22869

CVE-2025-47913

CVE-2026-46597

CVE-2026-39829

CVE-2026-39832

Jira Trackers

OCPBUGS-98108

OCPBUGS-95492

AI-generated. Review for accuracy.

@prabhapa requested in Slack thread

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

prabhapa · 2026-09-10T09:49:18Z

/jira refresh

openshift-ci-robot · 2026-09-10T09:49:23Z

@prabhapa: This pull request references Jira Issue OCPBUGS-98108, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

This pull request references Jira Issue OCPBUGS-95492, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

prabhapa · 2026-09-10T12:47:13Z

/jira refresh

openshift-ci-robot · 2026-09-10T12:47:19Z

@prabhapa: This pull request references Jira Issue OCPBUGS-98108, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

This pull request references Jira Issue OCPBUGS-95492, which is valid. The bug has been moved to the POST state.

4 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (5.0.0) matches configured target version for branch (5.0.0)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"

No GitHub users were found matching the public email listed for the QA contact in Jira (ppalepu@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

prabhapa · 2026-09-10T12:55:59Z

/jira refresh

openshift-ci-robot · 2026-09-10T12:56:07Z

@prabhapa: This pull request references Jira Issue OCPBUGS-98108, which is valid. The bug has been moved to the POST state.

4 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (5.0.0) matches configured target version for branch (5.0.0)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"

No GitHub users were found matching the public email listed for the QA contact in Jira (ppalepu@redhat.com), skipping review request.

This pull request references Jira Issue OCPBUGS-95492, which is valid.

4 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (5.0.0) matches configured target version for branch (5.0.0)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"

No GitHub users were found matching the public email listed for the QA contact in Jira (ppalepu@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

prabhapa · 2026-09-10T13:33:08Z

/test images

openshift-merge-bot · 2026-09-10T14:00:33Z

/retest-required

Remaining retests: 0 against base HEAD 35b0a13 and 2 for PR HEAD 535502d in total

openshift-ci · 2026-09-10T14:09:19Z

@redhat-chai-bot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/security	`535502d`	link	false	`/test security`

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

prabhapa · 2026-09-15T04:59:54Z

/test images

openshift-ci-robot · 2026-09-15T05:13:38Z

@redhat-chai-bot: Jira Issue Verification Checks: Jira Issue OCPBUGS-98108
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-98108 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Jira Issue OCPBUGS-95492: Some pull requests linked via external trackers have merged:

openshift/builder#550

The following pull request, linked via external tracker, has not merged:

openshift/builder#557 is open

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-95492 has not been moved to the MODIFIED state.

This PR is marked as verified. If the remaining PRs listed above are marked as verified before merging, the issue will automatically be moved to VERIFIED after all of the changes from the PRs are available in an accepted nightly payload.

Details

In response to this:

Summary

Bumps golang.org/x/crypto using the openshift-sustaining/crypto security fork (version v0.33.0-sec.5) to address multiple crypto CVEs.

Fork version selected based on Go minimum version 1.22.8 (Go >= 1.20, < 1.23 range).

CVEs Fixed

CVE-2025-22869

CVE-2025-47913

CVE-2026-46597

CVE-2026-39829

CVE-2026-39832

Jira Trackers

OCPBUGS-98108

OCPBUGS-95492

AI-generated. Review for accuracy.

@prabhapa requested in Slack thread

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

OCPBUGS-98108,OCPBUGS-95492: Bump golang.org/x/crypto to fix CVE-2025…

535502d

…-22869,CVE-2025-47913,CVE-2026-46597,CVE-2026-39829,CVE-2026-39832

openshift-ci Bot requested review from divyansh42 and moebasim September 1, 2026 07:44

openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Sep 2, 2026

openshift-ci Bot assigned moebasim Sep 2, 2026

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Sep 2, 2026

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 2, 2026

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 3, 2026

openshift-ci Bot added the jira/skip-dependent-bug-check Indicates that the referenced Jira bug does not require a dependent bug. label Sep 10, 2026

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 10, 2026

openshift-ci Bot merged commit 1e53243 into openshift:release-5.0 Sep 15, 2026
10 of 11 checks passed

Uh oh!

Conversation

redhat-chai-bot commented Sep 1, 2026

Summary

CVEs Fixed

Jira Trackers

Uh oh!

coderabbitai Bot commented Sep 1, 2026

Review skipped

Uh oh!

openshift-ci-robot commented Sep 1, 2026

Summary

CVEs Fixed

Jira Trackers

Uh oh!

openshift-merge-bot Bot commented Sep 1, 2026

Uh oh!

prabhapa commented Sep 1, 2026

Uh oh!

openshift-merge-bot Bot commented Sep 1, 2026

Uh oh!

prabhapa commented Sep 2, 2026

Uh oh!

prabhapa commented Sep 2, 2026

Uh oh!

moebasim commented Sep 2, 2026

Uh oh!

moebasim commented Sep 2, 2026

Uh oh!

openshift-ci-robot commented Sep 2, 2026

Uh oh!

openshift-merge-bot Bot commented Sep 2, 2026

Uh oh!

openshift-ci Bot commented Sep 2, 2026

Uh oh!

prabhapa commented Sep 3, 2026

Uh oh!

openshift-ci-robot commented Sep 3, 2026

Uh oh!

prabhapa commented Sep 3, 2026

Uh oh!

openshift-ci-robot commented Sep 3, 2026

Uh oh!

prabhapa commented Sep 9, 2026

Uh oh!

prabhapa commented Sep 10, 2026

Uh oh!

openshift-ci-robot commented Sep 10, 2026

Summary

CVEs Fixed

Jira Trackers

Uh oh!

prabhapa commented Sep 10, 2026

Uh oh!

openshift-ci-robot commented Sep 10, 2026

Uh oh!

prabhapa commented Sep 10, 2026

Uh oh!

openshift-ci-robot commented Sep 10, 2026

Uh oh!

prabhapa commented Sep 10, 2026

Uh oh!

openshift-ci-robot commented Sep 10, 2026

Uh oh!

prabhapa commented Sep 10, 2026

Uh oh!

openshift-merge-bot Bot commented Sep 10, 2026

Uh oh!

openshift-ci Bot commented Sep 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

prabhapa commented Sep 15, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented Sep 15, 2026

Summary

CVEs Fixed

Jira Trackers

Uh oh!

Reviewers

openshift-ci Bot commented Sep 10, 2026 •

edited

Loading