Skip to content

[release-4.14] OCPBUGS-88422: Bump axios to ^0.33.0 Addresses CVE-2026-44486 - #16789

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.14from
rhdmalone:release-4.14-axios-bump
Jul 24, 2026
Merged

[release-4.14] OCPBUGS-88422: Bump axios to ^0.33.0 Addresses CVE-2026-44486#16789
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.14from
rhdmalone:release-4.14-axios-bump

Conversation

@rhdmalone

@rhdmalone rhdmalone commented Jul 21, 2026

Copy link
Copy Markdown

OCPBUGS-88422: Bump axios to ^0.33.0 Addresses CVE-2026-44486
https://redhat.atlassian.net/browse/OCPBUGS-88422

Steps involved in Axios bump for release-4.14:

  1. Edit frontend/package.json
    update references to axios version in package.json to "axios": "^0.33.0",

  2. Reinstall lockfile
    cd frontend
    yarn install

Testing:
from repo root/

./build-frontend.sh
./build-demos.sh

from frontend/
yarn build
Output from the above steps was analysed by Claude - no issues

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@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/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jul 21, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@rhdmalone: This pull request references Jira Issue OCPBUGS-88422, 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.14.z) matches configured target version for branch (4.14.z)
  • bug is in the state ASSIGNED, 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-88427 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-88427 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@redhat.com), skipping review request.

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

Details

In response to this:

OCPBUGS-88422: Bump axios to ^0.33.0 Addresses CVE-2026-44486
https://redhat.atlassian.net/browse/OCPBUGS-88422

Steps involved in Axios bump for release-4.14:

  1. Edit frontend/package.json
    update axios version in package.json to "axios": "^0.33.0",

  2. Reinstall lockfile
    cd frontend
    yarn install

Testing:
from repo root/

./build-frontend.sh
./build-demos.sh

from frontend/
yarn build
Output from the above steps was analysed by Claude - no issues

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

coderabbitai Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

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: a87d7cce-4f90-4ee5-b689-8afaa9155527

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

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

@openshift-ci
openshift-ci Bot requested review from Leo6Leo and sg00dwin July 21, 2026 10:33
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@rhdmalone: This pull request references Jira Issue OCPBUGS-88422, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.z) matches configured target version for branch (4.14.z)
  • bug is in the state POST, 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-88427 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-88427 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@redhat.com), skipping review request.

Details

In response to this:

OCPBUGS-88422: Bump axios to ^0.33.0 Addresses CVE-2026-44486
https://redhat.atlassian.net/browse/OCPBUGS-88422

Steps involved in Axios bump for release-4.14:

  1. Edit frontend/package.json
    update references to axios version in package.json to "axios": "^0.33.0",

  2. Reinstall lockfile
    cd frontend
    yarn install

Testing:
from repo root/

./build-frontend.sh
./build-demos.sh

from frontend/
yarn build
Output from the above steps was analysed by Claude - no issues

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.

@rhdmalone rhdmalone changed the title OCPBUGS-88422: Bump axios to ^0.33.0 Addresses CVE-2026-44486 [release-4.14] OCPBUGS-88422: Bump axios to ^0.33.0 Addresses CVE-2026-44486 Jul 21, 2026
@rhdmalone

Copy link
Copy Markdown
Author

/verified by CI

@openshift-ci-robot

Copy link
Copy Markdown
Contributor

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

Details

In response to this:

/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-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jul 21, 2026

@logonoff logonoff left a comment

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.

/lgtm

@logonoff

Copy link
Copy Markdown
Member

/label backport-risk-assessed

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jul 21, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 21, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling required tests:
/test e2e-gcp-console

@openshift-ci

openshift-ci Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: logonoff, rhdmalone

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 Jul 21, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 63e29cb and 2 for PR HEAD 570e4f0 in total

@rhdmalone

Copy link
Copy Markdown
Author

/test e2e-gcp-console

3 similar comments
@rhdmalone

Copy link
Copy Markdown
Author

/test e2e-gcp-console

@rhdmalone

Copy link
Copy Markdown
Author

/test e2e-gcp-console

@rhdmalone

Copy link
Copy Markdown
Author

/test e2e-gcp-console

@rhdmalone

Copy link
Copy Markdown
Author

hi @germanparente
I asked Claude to check if the failing e2e-gcp-console test was in any way related to the Axios bump.
Claude has found that the failing test is not caused by the Axios bump.

Details here:

e2e-gcp-console failure — unrelated to axios bump

The failing e2e-gcp-console run is not caused by commit 570e4f0 (axios ^0.31.1 → ^0.33.0).

This PR only changes frontend/package.json and frontend/yarn.lock. No UI, Pipelines, or Cypress test code was modified. analyze, backend, frontend, and images are green.

Actual failure is in e2e/pipeline-ci.feature: after installing Red Hat OpenShift Pipelines, Cypress timed out waiting for the pipeline builder header to become visible because its parent drawer stayed display: none (waitForPipelineTasks). Remaining scenarios were skipped because this happened in a before-all hook.

This is unrelated to axios because:

  • the failure is Pipelines operator install / UI readiness, not HTTP client behavior
  • axios is only used in kubevirt CDI upload paths in this codebase
  • related upload/secrets Cypress tests passed in the same job
  • the diff is a dependency-only bump with no application code changes

This looks like a known flaky Pipelines UI readiness issue.

/test e2e-gcp-console

@germanparente

Copy link
Copy Markdown
Contributor

Since the assessment has shown the test as flaky and not related to PR:

/override ci/prow/e2e-gcp-console

@openshift-ci

openshift-ci Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

@germanparente: Overrode contexts on behalf of germanparente: ci/prow/e2e-gcp-console

Details

In response to this:

Since the assessment has shown the test as flaky and not related to PR:

/override ci/prow/e2e-gcp-console

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.

@openshift-ci

openshift-ci Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

@rhdmalone: 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/e2e-gcp-console 570e4f0 link true /test e2e-gcp-console

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.

@openshift-merge-bot
openshift-merge-bot Bot merged commit 5e1c925 into openshift:release-4.14 Jul 24, 2026
7 checks passed
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@rhdmalone: Jira Issue Verification Checks: Jira Issue OCPBUGS-88422
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-88422 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

OCPBUGS-88422: Bump axios to ^0.33.0 Addresses CVE-2026-44486
https://redhat.atlassian.net/browse/OCPBUGS-88422

Steps involved in Axios bump for release-4.14:

  1. Edit frontend/package.json
    update references to axios version in package.json to "axios": "^0.33.0",

  2. Reinstall lockfile
    cd frontend
    yarn install

Testing:
from repo root/

./build-frontend.sh
./build-demos.sh

from frontend/
yarn build
Output from the above steps was analysed by Claude - no issues

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-merge-robot

Copy link
Copy Markdown
Contributor

Fix included in release 4.14.0-0.nightly-2026-07-25-041325

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants