CVE-2025-61927

HIGHPre-NVD 7.27.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (50th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2025-33777 (ENISA EUVD)Source: ENISA EUVD

7.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.2Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Happy DOM is a JavaScript implementation of a web browser without its graphical user interface. Happy DOM v19 and lower contains a security vulnerability that puts the owner system at the risk of RCE (Remote Code Execution) attacks. A Node.js VM Context is not an isolated environment, and if the user runs untrusted JavaScript code within the Happy DOM VM Context, it may escape the VM and get access to process level functionality. It seems like what the attacker can get control over depends on if the process is using ESM or CommonJS. With CommonJS the attacker can get hold of the require() function to import modules. Happy DOM has JavaScript evaluation enabled by default. This may not be obvious to the consumer of Happy DOM and can potentially put the user at risk if untrusted code is executed within the environment. Version 20.0.0 patches the issue by changing JavaScript evaluation to be disabled by default.

CVSS v3
7.2
EG Score
7.2HIGHmedium confidence
EG Risk
48
EG Risk 48/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity72% × 45%
Impact severity (EG Severity): CVSS 7.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
50th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.2): severity, escalated by confirmed exploitation. This CVE's 7.2 is its impact severity (EG Severity), not escalated.

EG Severity
7.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 10, 2025

Last Modified

October 8, 2026

Advisory Details (2)

Auto-updated Oct 8, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Escape of VM Context gives access to process level functionality · Advisory · capricorn86/happy-dom · GitHub

https://github.com/capricorn86/happy-dom/security/advisories/GHSA-37j7-fg3j-429f
GitHub commit Patch Available

commit 819d15ba2894 (capricorn86/happy-dom)

Patch available: capricorn86/happy-dom v20.10.5 (contains commit 819d15ba2894)

https://github.com/capricorn86/happy-dom/commit/819d15ba289495439eda8be360d92a614ce22405

Vendor Advisories for CVE-2025-61927(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatdevspaces/traefik-rhel9:3.25.0-17648924662025-12-15redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
happy-dom—
  • every version up to 20.0.0: fixed in 20.0.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 43× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 229 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 134 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-31 02:11 UTCEG score recompute
  2. 2026-10-31 02:11 UTCVendor advisory
  3. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  4. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  5. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  6. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  7. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  8. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  9. 2026-10-25 16:14 UTCEG score recompute
  10. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  11. 2026-10-24 14:22 UTCEG score recompute
  12. 2026-10-24 14:22 UTCVendor advisory
  13. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  14. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  15. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  16. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  17. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  18. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  19. 2026-10-18 05:22 UTCEG score recompute
  20. 2026-10-18 02:32 UTCEG score recompute
  21. 2026-10-18 02:32 UTCVendor advisory
  22. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  23. 2026-10-16 16:39 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  24. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  25. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
Show 70 more
  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  2. 2026-10-12 16:51 UTCEG score recompute
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  4. 2026-10-11 20:26 UTCEG score recompute
  5. 2026-10-11 18:37 UTCEG score recompute
  6. 2026-10-11 15:13 UTCEG score recompute
  7. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  9. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  10. 2026-10-08 17:10 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  11. 2026-10-08 15:00 UTCEG score recompute
  12. 2026-10-08 15:00 UTCVendor advisory
  13. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  14. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  15. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  16. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  17. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  18. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  19. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  20. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  21. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  22. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  23. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  24. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  25. 2026-09-21 04:19 UTCOSV refresh
  26. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  27. 2026-09-19 15:42 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  28. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  29. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  30. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  31. 2026-09-15 03:10 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  32. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  33. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  34. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  35. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  36. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  37. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  38. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  39. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  40. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  41. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  42. 2026-09-02 01:58 UTCOSV refresh
  43. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  44. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  45. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  46. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  47. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  48. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  49. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  50. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  51. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  52. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  53. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  54. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  55. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  56. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  57. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  58. 2026-08-16 05:08 UTCOSV refresh
  59. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  60. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  61. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  62. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  63. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  64. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  65. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  66. 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  67. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  68. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  69. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  70. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.6% · 45th percentile

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-61927?
CVE-2025-61927 is a high-severity vulnerability; its CVE record was published on October 10, 2025. Happy DOM is a JavaScript implementation of a web browser without its graphical user interface. Happy DOM v19 and lower contains a security vulnerability that puts the owner system at the risk of RCE (Remote Code Execution) attacks. A Node.js VM Context is not an isolated environment, and if the…
When was the CVE record for CVE-2025-61927 published?
The CVE record for CVE-2025-61927 was published on October 10, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2025-61927 actively exploited?
CVE-2025-61927 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-61927?
CVE-2025-61927 has a CVSS base score of 7.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-61927?
A fix for CVE-2025-61927 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-61927 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-61927

Explore →

Is Your Infrastructure Affected by CVE-2025-61927?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs