Skip to content

Fix for OCPBUGS-92073: CVE-2026-44990 - #16724

Merged
openshift-merge-bot[bot] merged 3 commits into
openshift:release-4.22from
germanparente:fix-CVE-2026-44990-release-4.22
Aug 20, 2026
Merged

Fix for OCPBUGS-92073: CVE-2026-44990#16724
openshift-merge-bot[bot] merged 3 commits into
openshift:release-4.22from
germanparente:fix-CVE-2026-44990-release-4.22

Conversation

@germanparente

Copy link
Copy Markdown
Contributor

Summary

  • Bump sanitize-html from ^2.3.2 to ^2.17.4 to fix CVE-2026-44990
  • CVE-2026-44990 is a stored XSS vulnerability (CVSS 9.3 Critical) in sanitize-html < 2.17.4 where content inside a disallowed <xmp> element can bypass sanitization

References

@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. labels Jul 7, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@germanparente: This pull request references Jira Issue OCPBUGS-92073, which is invalid:

  • expected Jira Issue OCPBUGS-92073 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

  • Bump sanitize-html from ^2.3.2 to ^2.17.4 to fix CVE-2026-44990
  • CVE-2026-44990 is a stored XSS vulnerability (CVSS 9.3 Critical) in sanitize-html < 2.17.4 where content inside a disallowed <xmp> element can bypass sanitization

References

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 jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jul 7, 2026
@openshift-ci
openshift-ci Bot requested review from jhadvig and rhamilto July 7, 2026 18:40
@germanparente

Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@germanparente: This pull request references Jira Issue OCPBUGS-92073, which is invalid:

  • expected dependent Jira Issue OCPBUGS-92088 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is Closed (Obsolete) 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.

@germanparente

Copy link
Copy Markdown
Contributor Author

As this has been fixed in 5.0, check OCPBUGS-92088:

"expected dependent OCPBUGS-92088 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is Closed (Obsolete) instead"

/label jira/skip-dependent-bug-check

@openshift-ci openshift-ci Bot added the jira/skip-dependent-bug-check Indicates that the referenced Jira bug does not require a dependent bug. label Aug 11, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@germanparente: An error was encountered querying GitHub for users with public email (ocp-sustaining-admins@redhat.com) for bug OCPBUGS-92073 on the Jira server at https://redhat.atlassian.net. No known errors were detected, please see the full error message for details.

Full error message. Post "http://ghproxy/graphql": dial tcp 172.30.229.2:80: connect: connection refused

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

Details

In response to this:

Summary

  • Bump sanitize-html from ^2.3.2 to ^2.17.4 to fix CVE-2026-44990
  • CVE-2026-44990 is a stored XSS vulnerability (CVSS 9.3 Critical) in sanitize-html < 2.17.4 where content inside a disallowed <xmp> element can bypass sanitization

References

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 jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 11, 2026
@germanparente

Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@germanparente: An error was encountered querying GitHub for users with public email (ocp-sustaining-admins@redhat.com) for bug OCPBUGS-92073 on the Jira server at https://redhat.atlassian.net. No known errors were detected, please see the full error message for details.

Full error message. Post "http://ghproxy/graphql": dial tcp 172.30.229.2:80: connect: connection refused

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

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.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@germanparente
germanparente force-pushed the fix-CVE-2026-44990-release-4.22 branch from eab6827 to c71c75e Compare August 11, 2026 10:43
@jhadvig

jhadvig commented Aug 14, 2026

Copy link
Copy Markdown
Member

/retest

@germanparente

Copy link
Copy Markdown
Contributor Author

/test frontend

@germanparente

Copy link
Copy Markdown
Contributor Author

/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 Aug 18, 2026
@germanparente

Copy link
Copy Markdown
Contributor Author

/test frontend

1 similar comment
@germanparente

Copy link
Copy Markdown
Contributor Author

/test frontend

@germanparente

Copy link
Copy Markdown
Contributor Author

frontend test failure assessment

Not related to this PR.

This PR only modifies frontend/package.json and frontend/yarn.lock to fix CVE-2026-44990. It does not change any application code, test code, or build configuration.

Failure details

The frontend test failed due to a husky permissions error in the CI container environment:

EPERM: operation not permitted, copyfile → .husky/_/husky.sh

This is a CI infrastructure issue — husky's postinstall hook failed to copy files into .husky/_/ due to filesystem permissions in the build container. All PatternFly dependency resolution checks passed with "No issues detected".

/retest should resolve this.

@germanparente

Copy link
Copy Markdown
Contributor Author

from former assessment,

/override ci/prow/frontend

@openshift-ci

openshift-ci Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

@germanparente: Overrode contexts on behalf of germanparente: ci/prow/frontend

Details

In response to this:

from former assessment,

/override ci/prow/frontend

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.

@jkaurredhat

Copy link
Copy Markdown

/lgtm

Skip husky installation when OPENSHIFT_CI is set to avoid EPERM errors
in the CI container environment during yarn postinstall.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Aug 19, 2026
@logonoff

Copy link
Copy Markdown
Member

/lgtm
/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Aug 19, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

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

Details

In response to this:

/lgtm
/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 openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 19, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-gcp-console

@germanparente

Copy link
Copy Markdown
Contributor Author

/test frontend

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 784dccd and 2 for PR HEAD 1c4a540 in total

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 28141c4 and 1 for PR HEAD 1c4a540 in total

@germanparente

Copy link
Copy Markdown
Contributor Author

/test frontend

@logonoff

Copy link
Copy Markdown
Member

/lgtm cancel
/label tide/merge-method-squash

fix this by running yarn dedupe and committing the changes

@openshift-ci openshift-ci Bot added tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. and removed lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Aug 20, 2026
Consolidate duplicate dayjs entries (1.10.7 → 1.11.21).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@openshift-ci-robot openshift-ci-robot removed the verified Signifies that the PR passed pre-merge verification criteria label Aug 20, 2026
@logonoff

Copy link
Copy Markdown
Member

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 20, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-gcp-console

@openshift-ci

openshift-ci Bot commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: germanparente, jkaurredhat, logonoff

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 Aug 20, 2026
@germanparente

Copy link
Copy Markdown
Contributor Author

/test e2e-gcp-console

@germanparente

Copy link
Copy Markdown
Contributor Author

/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Aug 20, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@germanparente: 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

openshift-ci Bot commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

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

@openshift-merge-bot
openshift-merge-bot Bot merged commit 537a21f into openshift:release-4.22 Aug 20, 2026
8 checks passed
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@germanparente: Jira Issue Verification Checks: Jira Issue OCPBUGS-92073
✔️ 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-92073 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:

Summary

  • Bump sanitize-html from ^2.3.2 to ^2.17.4 to fix CVE-2026-44990
  • CVE-2026-44990 is a stored XSS vulnerability (CVSS 9.3 Critical) in sanitize-html < 2.17.4 where content inside a disallowed <xmp> element can bypass sanitization

References

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.

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/skip-dependent-bug-check Indicates that the referenced Jira bug does not require a dependent bug. 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. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. 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