[release-4.19] OCPBUGS-82806: Address CVE-2026-35469

[ocp-sustaining-admins]

This is an automated PR from the ARC system.

This change addresses CVE-2026-35469 by updating github.com/moby/spdystream to v0.5.1, github.com/moby/spdystream/spdy to v0.5.1 on branch release-4.19.

Go version used: go1.23.12

Modules affected: .

The commands used to generate this PR were:

go get github.com/moby/spdystream@v0.5.1

go get github.com/moby/spdystream/spdy@v0.5.1

go mod tidy
go mod vendor

A member of the Red Hat Openshift Sustaining Team will review the PR and take appropriate action.

/assign @rh-akhatavk

Common PR issues and how to fix them:

1. Title needs to be changed:
   This might be needed if a PR references multiple Jira issues and some of them have been closed as duplicates.
   Use /retitle <NEW TITLE> command from openshift-ci bot
   openshift-ci bot commands

2. verify-commits check is failing:
   Commits need to be in the format UPSTREAM: <carry | drop | PR NUMBER>: <commit message>. You can do this by cloning the ARC fork and using git commit --amend -m <commit message>
   verify-commits documentation

[openshift-ci-robot]

@ocp-sustaining-admins: This pull request references Jira Issue OCPBUGS-82806, 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-82806 to depend on a bug targeting a version in 4.20.0, 4.20.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:

This is an automated PR from the ARC system.

This change addresses CVE-2026-35469 by updating github.com/moby/spdystream to v0.5.1, github.com/moby/spdystream/spdy to v0.5.1 on branch release-4.19.

Go version used: go1.23.12

Modules affected: .

The commands used to generate this PR were:

go get github.com/moby/spdystream@v0.5.1

go get github.com/moby/spdystream/spdy@v0.5.1

go mod tidy
go mod vendor

A member of the Red Hat Openshift Sustaining Team will review the PR and take appropriate action.

/assign @rh-akhatavk

Common PR issues and how to fix them:

1. Title needs to be changed:
   This might be needed if a PR references multiple Jira issues and some of them have been closed as duplicates.
   Use /retitle <NEW TITLE> command from openshift-ci bot
   openshift-ci bot commands

2. verify-commits check is failing:
   Commits need to be in the format UPSTREAM: <carry | drop | PR NUMBER>: <commit message>. You can do this by cloning the ARC fork and using git commit --amend -m <commit message>
   verify-commits documentation

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.

[coderabbitai]

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: Enterprise

Run ID: 134aec4b-c0ba-4a92-9921-bc7c9ee69c45

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

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[openshift-ci]

Hi @ocp-sustaining-admins. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[mpatlasov]

/ok-to-test

[openshift-ci]

@ocp-sustaining-admins: 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.

[mpatlasov]

/lgtm
/approve
/label backport-risk-assessed
/verified by CI

[openshift-ci-robot]

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

Details

In response to this:

/lgtm
/approve
/label backport-risk-assessed
/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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mpatlasov, ocp-sustaining-admins

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

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