OCPBUGS-74114: Bump keystonemiddleware version to 10.7.1-0.20260216144200.4c001ba for CVE-2026-22797 fix

[mabulgu]

Summary

Update the required version of keystonemiddleware to 10.7.1-0.20260216144200.4c001ba to address
CVE-2026-22797.

CVE Details

CVE-2026-22797 (CVSS 9.9 - Important)

The external_oauth2_token middleware in keystonemiddleware fails to sanitize
incoming authentication headers before processing OAuth 2.0 tokens. By sending
forged identity headers such as X-Is-Admin-Project, X-Roles, or X-User-Id,
an authenticated attacker may escalate privileges or impersonate other users.

• https://www.cve.org/CVERecord?id=CVE-2026-22797
• https://launchpad.net/bugs/2129018

Affected versions

keystonemiddleware 10.5 through 10.7 (before 10.7.2), 10.8 and 10.9 (before
10.9.1), and 10.10 through 10.12 (before 10.12.1).

Tracking

• OCPBUGS-76935 (4.22)
• OCPBUGS-76934 (4.21)
• OCPBUGS-74117 (4.20)
• OCPBUGS-74116 (4.19)
• OCPBUGS-74115 (4.18)
• OCPBUGS-74114 (4.17)

Fix

This PR bumps keystonemiddleware to 10.7.1-0.20260216144200.4c001ba for the release branch 4.17.

[openshift-ci-robot]

@mabulgu: This pull request references Jira Issue OCPBUGS-74114, 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 dependent Jira Issue OCPBUGS-74115 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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

Update the required version of keystonemiddleware to 10.7.1-0.20260216144200.4c001ba to address
CVE-2026-22797.

CVE Details

CVE-2026-22797 (CVSS 9.9 - Important)

The external_oauth2_token middleware in keystonemiddleware fails to sanitize
incoming authentication headers before processing OAuth 2.0 tokens. By sending
forged identity headers such as X-Is-Admin-Project, X-Roles, or X-User-Id,
an authenticated attacker may escalate privileges or impersonate other users.

• https://www.cve.org/CVERecord?id=CVE-2026-22797
• https://launchpad.net/bugs/2129018

Affected versions

keystonemiddleware 10.5 through 10.7 (before 10.7.2), 10.8 and 10.9 (before
10.9.1), and 10.10 through 10.12 (before 10.12.1).

Tracking

• OCPBUGS-76935 (4.22)
• OCPBUGS-76934 (4.21)
• OCPBUGS-74117 (4.20)
• OCPBUGS-74116 (4.19)
• OCPBUGS-74115 (4.18)
• OCPBUGS-74114 (4.17)

Fix

This PR bumps keystonemiddleware to 10.7.1-0.20260216144200.4c001ba for the release branch 4.17.

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.

[mabulgu]

/jira refresh

[openshift-ci-robot]

@mabulgu: This pull request references Jira Issue OCPBUGS-74114, which is invalid:

• expected dependent Jira Issue OCPBUGS-74115 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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.

[elfosardo]

/approve
/label backport-risk-assessed
/verfied bypass

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elfosardo, mabulgu

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 [elfosardo]

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

[openshift-ci]

@mabulgu: 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/images	8490350	link	true	/test images

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.

[mabulgu]

This is also tagged for production:

(.venv) ➜  ironic-ocp-tools git:(master) ironic-builds tag production ocp-4.17 python-keystonemiddleware-10.7.1-0.20260216144200.4c001ba.el9
Validating sources...
Tagging builds...
Tagging python-keystonemiddleware-10.7.1-0.20260216144200.4c001ba.el9 in rhaos-4.17-ironic-rhel-9-candidate
Watching tasks (this may be safely interrupted)...
70281584 tagBuild (noarch): free
70281584 tagBuild (noarch): free -> closed
  0 free  0 open  1 done  0 failed

70281584 tagBuild (noarch) completed successfully
Done!

@elfosardo could you override the images build to move on?

[mabulgu]

/jira refresh

[openshift-ci-robot]

@mabulgu: This pull request references Jira Issue OCPBUGS-74114, which is invalid:

• expected dependent Jira Issue OCPBUGS-74115 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

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.