Skip to content

CVE-2024-45337, CVE-2025-22869: Bump podman to v5.5.2 that fixes vulnerability in golang.org/x/crypto package#1974

Merged
openshift-merge-bot[bot] merged 2 commits intoopenshift:release-rhel8from
kunalmemane:CVE-2024-45337-CVE-2025-22869-rhel8
Feb 6, 2026
Merged

CVE-2024-45337, CVE-2025-22869: Bump podman to v5.5.2 that fixes vulnerability in golang.org/x/crypto package#1974
openshift-merge-bot[bot] merged 2 commits intoopenshift:release-rhel8from
kunalmemane:CVE-2024-45337-CVE-2025-22869-rhel8

Conversation

@kunalmemane
Copy link
Copy Markdown
Member

CVE-2024-45337, CVE-2025-22869: Bump podman to v5.5.2 that fixes vulnerability in golang.org/x/crypto package.

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@kunalmemane: No Jira issue with key CVE-2024 exists in the tracker at https://issues.redhat.com/.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

Details

In response to this:

CVE-2024-45337, CVE-2025-22869: Bump podman to v5.5.2 that fixes vulnerability in golang.org/x/crypto package.

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-ci-robot
Copy link
Copy Markdown
Contributor

@kunalmemane: No Jira issue with key CVE-2025 exists in the tracker at https://issues.redhat.com/.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

Details

In response to this:

CVE-2024-45337, CVE-2025-22869: Bump podman to v5.5.2 that fixes vulnerability in golang.org/x/crypto package.

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-ci openshift-ci Bot requested review from avinal and k37y July 2, 2025 11:37
@kunalmemane
Copy link
Copy Markdown
Member Author

/retest

3 similar comments
@kunalmemane
Copy link
Copy Markdown
Member Author

/retest

@kunalmemane
Copy link
Copy Markdown
Member Author

/retest

@kunalmemane
Copy link
Copy Markdown
Member Author

/retest

@kunalmemane
Copy link
Copy Markdown
Member Author

/lifecycle frozen

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Nov 27, 2025

@kunalmemane: The lifecycle/frozen label cannot be applied to Pull Requests.

Details

In response to this:

/lifecycle frozen

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.

@k37y
Copy link
Copy Markdown
Contributor

k37y commented Jan 28, 2026

/lgtm

@openshift-ci openshift-ci Bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jan 28, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 6606610 and 2 for PR HEAD 98cb6df in total

@kunalmemane
Copy link
Copy Markdown
Member Author

/retest

@kunalmemane kunalmemane force-pushed the CVE-2024-45337-CVE-2025-22869-rhel8 branch from 98cb6df to 55b112e Compare February 3, 2026 09:15
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 3, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Feb 3, 2026

@kunalmemane: 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 55b112e 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.

@k37y
Copy link
Copy Markdown
Contributor

k37y commented Feb 6, 2026

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Feb 6, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Feb 6, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: k37y, kunalmemane

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:

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

@openshift-merge-bot openshift-merge-bot Bot merged commit 1ba4bae into openshift:release-rhel8 Feb 6, 2026
8 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants