cve.bz

CVE-2026-118660 capricorn86 happy-dom: SSRF

8.6 highEPSS 0.4%Fix available

High (8.6) in capricorn86 happy-dom. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in happy-dom 21.0.0.

On this page
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.

Severity

CVSS 3.1

8.6 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 35th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • happy-dom (npm): fixed in 21.0.0

Ask an AI about this CVE

Show the promptExplain CVE-2026-118660 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-118660?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-118660?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-118660 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
capricorn86 happy-dom< 21.0.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-c8p4-j97h-3vg8npmhappy-dom<21.0.021.0.0

Red Hat

Red Hat rates this Moderate.

ProductPackageStateAdvisory
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/gateway-rhel9Will not fix
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/gateway-rhel9Will not fix
Red Hat Ansible Automation Platform 2automation-gatewayOut of support scope
Red Hat Ansible Automation Platform 2automation-platform-uiWill not fix
Red Hat OpenShift AI (RHOAI)rhoai/odh-feature-server-rhel9Will not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-118660.

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON