OCPBUGS-88028: Bump follow-redirects from 1.15.3 to 1.16.0 to fix CVE-2026-40895

[amitesh1201]

Summary

• CVE: CVE-2026-40895 — Information disclosure via custom authentication headers in cross-domain redirects
• Package: follow-redirects → 1.16.0 (transitive dependency)
• Risk Level: LOW (development-only dependency, not in production)

Impact

• Production: NOT AFFECTED (webpack-dev-server and http-server are devDependencies, not deployed)
• Development: Potentially affected (local dev server only)

Changes

• Added yarn resolution for follow-redirects@^1.16.0 in frontend/package.json
• Added yarn resolution for follow-redirects@^1.16.0 in dynamic-demo-plugin/package.json
• Updated frontend/yarn.lock
• Updated dynamic-demo-plugin/yarn.lock

Test Plan

• yarn build succeeds (production build)
• dynamic-demo-plugin/ installs without errors

[openshift-ci-robot]

@amitesh1201: This pull request references Jira Issue OCPBUGS-88028, 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-88028 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, 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:

Summary

• CVE: CVE-2026-40895 — Information disclosure via custom authentication headers in cross-domain redirects
• Package: follow-redirects → 1.16.0 (transitive dependency)
• Risk Level: LOW (development-only dependency, not in production)

Affected Workspaces

Workspace	Old Version	New Version	Chain
frontend/	1.15.3	1.16.0	webpack-dev-server → http-proxy-middleware → http-proxy → follow-redirects
dynamic-demo-plugin/	1.15.11	1.16.0	http-server → http-proxy → follow-redirects

Impact

• Production: NOT AFFECTED (webpack-dev-server and http-server are devDependencies, not deployed)
• Development: Potentially affected (local dev server only)

Changes

• Added yarn resolution for follow-redirects@^1.16.0 in frontend/package.json
• Added yarn resolution for follow-redirects@^1.16.0 in dynamic-demo-plugin/package.json
• Updated frontend/yarn.lock
• Updated dynamic-demo-plugin/yarn.lock

Test Plan

• yarn test passes (frontend)
• yarn build succeeds (production build)
• yarn dev runs without errors (dev server)
• dynamic-demo-plugin/ installs without errors

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 NOT APPROVED

This pull-request has been approved by: amitesh1201
Once this PR has been reviewed and has the lgtm label, please assign jhadvig for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• dynamic-demo-plugin/OWNERS
• frontend/OWNERS

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

[openshift-ci]

@amitesh1201: 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.

[amitesh1201]

/jira refresh

[openshift-ci-robot]

@amitesh1201: This pull request references Jira Issue OCPBUGS-88028, which is invalid:

• expected Jira Issue OCPBUGS-88028 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, 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.

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.