Skip to content

[release-4.16] OCPBUGS-74316: Backport ansible-runner-http and fix CVE-2026-24049 by using wheel 0.46.3#74

Open
mytreya-rh wants to merge 5 commits intoopenshift:release-4.16from
mytreya-rh:fix_CVE-2026-21441_4.16
Open

[release-4.16] OCPBUGS-74316: Backport ansible-runner-http and fix CVE-2026-24049 by using wheel 0.46.3#74
mytreya-rh wants to merge 5 commits intoopenshift:release-4.16from
mytreya-rh:fix_CVE-2026-21441_4.16

Conversation

@mytreya-rh
Copy link
Copy Markdown
Contributor

Description of the change:
Fix CVE-2026-24049 with by using wheel 0.46.3
In addition fix CVE-2026-21441, CVE-2025-66471, and CVE-2025-66418 by bumping urllib3 to ~=2.6.3
Also backport "Install ansible_runner_http as local package" (commits: e4b92e0 and 1a59c6c) to simplify dependencies and make it easier to apply future CVE fixes.

Motivation for the change:
Reduce CVE Exposure

In addition fix CVE-2026-21441, CVE-2025-66471, and CVE-2025-66418 by bumping urllib3 to ~=2.6.3
Also backport "Install ansible_runner_http as local package" (commits: e4b92e0 and 1a59c6c) to simplify dependencies and make it easier to apply future CVE fixes.
@mytreya-rh mytreya-rh requested a review from chiragkyal March 21, 2026 19:23
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 21, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 21, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 720290ce-558c-49e9-85ab-6c81fc1a7dea

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
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci-robot
Copy link
Copy Markdown

@mytreya-rh: This pull request references Jira Issue OCPBUGS-74316, 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-74316 to depend on a bug targeting a version in 4.17.0, 4.17.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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:

Description of the change:
Fix CVE-2026-24049 with by using wheel 0.46.3
In addition fix CVE-2026-21441, CVE-2025-66471, and CVE-2025-66418 by bumping urllib3 to ~=2.6.3
Also backport "Install ansible_runner_http as local package" (commits: e4b92e0 and 1a59c6c) to simplify dependencies and make it easier to apply future CVE fixes.

Motivation for the change:
Reduce CVE Exposure

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.

…er/kube-rbac-proxy:v0.16.0 to registry.k8s.io/kubebuilder/kube-rbac-proxy:v0.16.0
@mytreya-rh mytreya-rh force-pushed the fix_CVE-2026-21441_4.16 branch 2 times, most recently from 35fb5d1 to eab9345 Compare March 22, 2026 11:13
…g requirements

Pin setuptools==75.3.0 and setuptools-scm==7.1.0 in requirements-pre-build.txt
so cachi2 fetches versions that satisfy build isolation constraints:
- ansible-runner requires setuptools>=45.2.0,<=75.3.0
- kubernetes requires setuptools_scm<8.0
The later requirements-build.txt steps upgrade both to their newer versions.

Made-with: Cursor
@mytreya-rh mytreya-rh force-pushed the fix_CVE-2026-21441_4.16 branch 2 times, most recently from 82b018c to 38b2390 Compare March 26, 2026 19:31
…on conflict

google-auth 2.49.1 requires cryptography>=38.0.3, but the RHEL 9 RPM
(python3-cryptography) only provides 36.0.1. Pin to 2.38.0 (matching the
current published operator image) and regenerate all requirements files.

Made-with: Cursor
@mytreya-rh mytreya-rh force-pushed the fix_CVE-2026-21441_4.16 branch from 38b2390 to 1dc7b68 Compare March 27, 2026 10:18
@chiragkyal
Copy link
Copy Markdown
Member

/retitle [release-4.16] OCPBUGS-74316: Backport ansible-runner-http and fix CVE-2026-24049 by using wheel 0.46.3

@openshift-ci openshift-ci bot changed the title OCPBUGS-74316: release-4.16 Fix CVE-2026-24049 with by using wheel 0.46.3 [release-4.16] OCPBUGS-74316: Backport ansible-runner-http and fix CVE-2026-24049 by using wheel 0.46.3 Mar 27, 2026
@chiragkyal
Copy link
Copy Markdown
Member

chiragkyal commented Mar 27, 2026

Copy link
Copy Markdown
Member

@chiragkyal chiragkyal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!
I'll add the labels whenever the unit test CI passes. Thanks!

# Ref: https://github.com/operator-framework/ansible-operator-plugins/pull/67#issuecomment-2189164688
# NOTE: This ignored vulnerability (74261) was detected in ansible-core, \
# but the fix is not available in any 2.15.z version of ansible-core as it has already reached EOL, See: \
# - https://docs.ansible.com/ansible/latest/reference_appendices/release_and_maintenance.html#ansible-core-support-matrix
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: We can keep this URL for future reference.

The previous setup-envtest version downloaded envtest binaries
(kube-apiserver, etcd) from Google Cloud Storage, which now permanently
returns 401 Unauthorized. This caused the handler unit tests to fail
because KUBEBUILDER_ASSETS could not be resolved.

Update setup-envtest to a release-0.17 build (cb94c680f5d5) that
supports downloading from GitHub releases while remaining compatible
with Go 1.21 used in CI. Pass --use-deprecated-gcs=false in the
Makefile to opt into GitHub-based downloads.

Made-with: Cursor
@mytreya-rh mytreya-rh force-pushed the fix_CVE-2026-21441_4.16 branch from fbdd1f0 to 4e976e7 Compare April 4, 2026 11:25
@openshift-ci
Copy link
Copy Markdown

openshift-ci bot commented Apr 4, 2026

@mytreya-rh: all tests passed!

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.

Copy link
Copy Markdown
Member

@chiragkyal chiragkyal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @mytreya-rh for this fix!
/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 5, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci bot commented Apr 5, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chiragkyal, mytreya-rh

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-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 5, 2026
@chiragkyal
Copy link
Copy Markdown
Member

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown

@chiragkyal: This pull request references Jira Issue OCPBUGS-74316, 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.

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

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.

@chiragkyal
Copy link
Copy Markdown
Member

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Apr 6, 2026
@openshift-ci-robot
Copy link
Copy Markdown

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

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.16.z) matches configured target version for branch (4.16.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-74319 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-74319 targets the "4.17.z" version, which is one of the valid target versions: 4.17.0, 4.17.z
  • bug has dependents

Requesting review from QA contact:
/cc @emmajiafan

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-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Apr 6, 2026
@openshift-ci openshift-ci bot requested a review from emmajiafan April 6, 2026 18:03
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. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. 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