CVE-2026-118660: Happy DOM: SSRF via iframe and link stylesheet when parsing untrusted HTML

Published Oct 28, 2026
·
Updated

Happy DOM is a JavaScript implementation of a web browser without its graphical user interface. Prior to 21.0.0, Happy DOM loads iframe src URLs and link rel="stylesheet" href URLs by default while parsing untrusted HTML on the server because disableIframePageLoading and disableCSSFileLoading default to false. An attacker who controls parsed HTML can therefore cause server-side requests to arbitrary internal or cloud endpoints without an application opt-in and may expose confidential responses or credentials returned by those endpoints. This issue is fixed in version 21.0.0.

Affected Software

1 affected component
npm/happy-dom<21.0.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Happy DOM to a version that resolves this vulnerability.

    Fixed in 21.0.0
  2. Configuration

    Set disableIframePageLoading and disableCSSFileLoading to true when parsing untrusted HTML to prevent loading iframe src and link rel="stylesheet" href URLs.

    Happy DOM disableIframePageLoading and disableCSSFileLoading = true

Event History

Oct 28, 2026
CVE Published
via MITRE·08:23 PM
Data Sourced
via MITRE·08:23 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this issue?

Applications using Happy DOM before 21.0.0 are exposed if they parse HTML that an attacker can control or influence on the server. The affected behavior can make requests to arbitrary internal or cloud endpoints reachable from that server.

2

Does this require an application to explicitly enable external resource loading?

No. Before 21.0.0, iframe page loading and CSS file loading are enabled by default because disableIframePageLoading and disableCSSFileLoading default to false.

3

What HTML content can trigger server-side requests?

An attacker-controlled iframe src URL or a link element with rel="stylesheet" and an href URL can trigger a request while the HTML is parsed.

4

What can be done if upgrading is not immediately possible?

Disable iframe page loading and CSS file loading by setting disableIframePageLoading and disableCSSFileLoading, and do not parse untrusted HTML with external resource loading enabled.

5

How can I determine whether my deployment is affected?

Check whether the application uses Happy DOM before version 21.0.0 and parses untrusted HTML. Also verify whether iframe and CSS file loading have been left enabled under their default settings.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203