CVE Intelligence
Medium Authentication

CVE-2026-118661 — Happy DOM: Cookie scope forgery: no DNS-label boundary on Domain= matching , attacker origin sets victim cookies

Happy DOM is a JavaScript implementation of a web browser without its graphical user interface. Prior to 20.14.6, Happy DOM's CookieContainer in src/cookie/CookieContainer.ts does not correctly validate or match Domain cookie attributes. It can accept a Domain unrelated to the origin setting the cookie, including a public suffix, and separately treats an unrelated suffix-sharing hostname as a match because cookieMatchesURL does not enforce a DNS-label boundary. In server-side rendering and prerendering applications that contact attacker-controlled origins and then make requests to a victim origin, these behaviors can plant and deliver a forged cookie, enabling cookie injection or session fixation. This issue is fixed in version 20.14.6.

Published Oct 28, 2026 · Updated Oct 29, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.3% (30-day exploitation probability)+3
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.27%
ahead of 20% of scored CVEs · Oct 29, 2026
Affects
Capricorn86
Happy Dom and 1 more
CVSS base
6.5
Medium · 3 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Npm Happy-dom: fixed in version 20.14.6 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Capricorn86 Happy Dom, Npm Happy-dom).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. Search available logs for exploit probes matching the vulnerability class (authentication), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Capricorn86 Happy Dom version < 20.14.6 Vulnerable CVE Program (cve.org) e CISA ADP
Npm Happy-dom ≤ 20.14.5 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.5 CVSS 3.1 Medium 3.9 2.5 security-advisories@github.com via NIST National Vulnerability Database
6.5 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
6.5 CVSS 3.1 Medium — — GitHub_M via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N (score shown at the top: security-advisories@github.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-565 · Reliance on Cookies without Validation and Integrity Checking

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Review authentication logs: logins without MFA, anomalous sessions and recently created accounts.
web/proxy/WAF logsnetwork IDS/IPSauthentication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Received → Awaiting Analysis
    Oct 29, 2026 · NIST National Vulnerability Database
  • Fix documented
    Oct 28, 2026 · GitHub Security Advisories
  • Affected products added · npm/happy-dom
    Oct 28, 2026 · GitHub Security Advisories
  • Affected products added · capricorn86/happy-dom
    Oct 28, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 28, 2026
  • CVSS changed · 6.5
    Oct 28, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 28, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 28, 2026 · Alertas do Telegram
  • CVE published
    Oct 28, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 28, 2026 – Oct 28, 2026
  • 1× Official description updated · Oct 28, 2026 – Oct 28, 2026

References

5 on the record

Elsewhere on this site

Capricorn86
every CVE for this vendor
Authentication
same class
CWE-565
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-118660 Happy DOM: SSRF via iframe and link stylesheet when parsing untrusted HTML 1d
  • CVE-2026-118659 @happy-dom/server-renderer: ServerRendererServer Target-Origin Bypass SSRF / Open Proxy 1d
  • CVE-2026-115895 Happy DOM: Incomplete fix for CVE-2026-33943: unsanitized import alias leads to host code execution 6d
  • CVE-2026-34226 Happy DOM's fetch credentials include uses page-origin cookies instead of target-origin cookies Mar 27, 2026
  • CVE-2026-33943 Happy DOM ECMAScriptModuleCompiler: unsanitized export names are interpolated as executable code Mar 27, 2026
  • CVE-2025-62410 --disallow-code-generation-from-strings is not sufficient for isolating untrusted JavaScript in happy-dom Oct 15, 2025

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-118661 is "Happy DOM: Cookie scope forgery: no DNS-label boundary on Domain= matching , attacker origin sets victim cookies", rated Medium. It affects Happy Dom (Capricorn86); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.5 describes technical severity. EPSS 0.27% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.