Fix CVE-2026-21441, CVE-2025-66471, and CVE-2025-66418 by bumping urllib3 to ~=2.6.3#199
Fix CVE-2026-21441, CVE-2025-66471, and CVE-2025-66418 by bumping urllib3 to ~=2.6.3#199mytreya-rh wants to merge 1 commit intooperator-framework:mainfrom
Conversation
|
@mytreya-rh: GitHub didn't allow me to request PR reviews from the following users: chiragkyal. Note that only operator-framework members and repo collaborators can review this PR, and authors cannot review their own PRs. DetailsIn response to this:
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. |
mytreya-rh
force-pushed
the
fix_CVE-2025-66471
branch
2 times, most recently
from
ceee207 to
065e439
Compare
|
/ok-to-test |
|
@chiragkyal: Cannot trigger testing until a trusted user reviews the PR and leaves an DetailsIn response to this:
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. |
operator-framework#191 by bumping urllib3 to 2.6.0 and operator-framework#197 operator-framework#198 by regenerating the Pipfile.lock
mytreya-rh
force-pushed
the
fix_CVE-2025-66471
branch
from
065e439 to
72ffbb1
Compare
3 participants
Description of the change:
Fix issues:
#191 by bumping urllib3 to 2.6.0
and
#197 #198 by regenerating the Pipfile.lock
Motivation for the change:
Closes #191
Closes #197
Closes #198
/cc @chiragkyal
/cc @acornett21