OCPBUGS-99032: Fix CVE-2026-49978 - bump DOMPurify to >= 3.4.7

[germanparente]

What this PR does / why we need it

CVE-2026-49978: DOMPurify IN_PLACE sanitization bypass via attached Shadow Root inside <template>.content (XSS). Affects DOMPurify versions <= 3.4.6.

monitoring-plugin has DOMPurify 3.2.7 as a transitive dependency via monaco-editor. This adds a dompurify override in package.json to bump it to ^3.4.11 (resolved to 3.4.12).

Which issue(s) this PR fixes

OCPBUGS-99032

Checklist

• Subject and description added to both, commit and PR.
• Relevant issues have been referenced.

[openshift-ci-robot]

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

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

What this PR does / why we need it

CVE-2026-49978: DOMPurify IN_PLACE sanitization bypass via attached Shadow Root inside <template>.content (XSS). Affects DOMPurify versions <= 3.4.6.

monitoring-plugin has DOMPurify 3.2.7 as a transitive dependency via monaco-editor. This adds a dompurify override in package.json to bump it to ^3.4.11 (resolved to 3.4.12).

Which issue(s) this PR fixes

OCPBUGS-99032

Checklist

• Subject and description added to both, commit and PR.
• Relevant issues have been referenced.

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]

/jira refresh

[openshift-ci-robot]

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

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

"expected dependent Jira Issue OCPBUGS-99041 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is Closed (Not a Bug) instead"

So,

/label jira/skip-dependent-bug-check

[openshift-ci-robot]

@germanparente: This pull request references Jira Issue OCPBUGS-99032, which is valid. The bug has been moved to the POST state.

4 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"

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:

What this PR does / why we need it

CVE-2026-49978: DOMPurify IN_PLACE sanitization bypass via attached Shadow Root inside <template>.content (XSS). Affects DOMPurify versions <= 3.4.6.

monitoring-plugin has DOMPurify 3.2.7 as a transitive dependency via monaco-editor. This adds a dompurify override in package.json to bump it to ^3.4.11 (resolved to 3.4.12).

Which issue(s) this PR fixes

OCPBUGS-99032

Checklist

• Subject and description added to both, commit and PR.
• Relevant issues have been referenced.

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]

/jira refresh

[openshift-ci-robot]

@germanparente: This pull request references Jira Issue OCPBUGS-99032, which is valid.

4 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"

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:

/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.

[openshift-ci]

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

[jgbernalp]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: germanparente, jgbernalp

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

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

[jgbernalp]

/label qe-approved

[openshift-ci-robot]

@germanparente: Jira Issue OCPBUGS-99032: All pull requests linked via external trackers have merged:

• openshift/monitoring-plugin#1085

Jira Issue OCPBUGS-99032 has been moved to the MODIFIED state.

Details

In response to this:

What this PR does / why we need it

CVE-2026-49978: DOMPurify IN_PLACE sanitization bypass via attached Shadow Root inside <template>.content (XSS). Affects DOMPurify versions <= 3.4.6.

monitoring-plugin has DOMPurify 3.2.7 as a transitive dependency via monaco-editor. This adds a dompurify override in package.json to bump it to ^3.4.11 (resolved to 3.4.12).

Which issue(s) this PR fixes

OCPBUGS-99032

Checklist

• Subject and description added to both, commit and PR.
• Relevant issues have been referenced.

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]

Fix included in release 4.22.0-0.nightly-2026-07-23-204519