CVE REMEDIATION GUIDE
Review reviewCriticalFixed-version data available

CVE-2026-33943 remediation guide

capricorn86 happy-dom, Red Hat Ansible Automation Platform 2, Red Hat OpenShift Container Platform 4

Happy DOM is a JavaScript implementation of a web browser without its graphical user interface. In versions 15.10.0 through 20.8.7, a code injection vulnerability in `ECMAScriptModuleCompiler` allows an attacker to achieve Remote Code Execution (RCE) by injecting arbitrary JavaScript expressions inside `export { }` declarations in ES module scripts processed by happy-dom. The compiler directly interpolates unsanitized content into generated code as an executable expression, and the quote filter does not strip backticks, allowing template literal-based payloads to bypass sanitization. Versio...

Open CVE record
Productcapricorn86 happy-dom, Red Hat Ansible Automation Platform 2, Red Hat OpenShift Container Platform 4
Affected versions>= >= 15.10.0, < 20.8.8, >= 15.10.0 < 20.8.8
Fixed versions20.8.8
Priority basisReview · CVSS 9.8 · EPSS 0.79%
01

Identify the affected asset

Confirm whether capricorn86 happy-dom, Red Hat Ansible Automation Platform 2, Red Hat OpenShift Container Platform 4 is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= >= 15.10.0, < 20.8.8, >= 15.10.0 < 20.8.8. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 20.8.8. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.

CVE-2026-33943 Remediation Guide | SECUFOCUS NOW