{"answers":{"affected":"2 open source packages ship an affected version, including happy-dom.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61927 exists.","fix":"Upgrade happy-dom to 20.0.0 or later.","what":"CVE-2025-61927 is a high-severity code injection vulnerability in capricorn86 happy-dom, published on 10 Oct 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-61927 and fix it if it is affected.\n\nWhat it is: CVE-2025-61927 is a high-severity code injection vulnerability in capricorn86 happy-dom, published on 10 Oct 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61927 exists.\n\nAffected packages and fixed versions:\n- happy-dom (npm): affected all versions; fixed in 20.0.0\n- happy-dom (npm): affected all versions; fixed in 20.0.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-61927/ (Markdown: https://insights.sbomify.com/CVE-2025-61927/index.md)","id":"CVE-2025-61927","markdown":"https://insights.sbomify.com/CVE-2025-61927/index.md","name":"CVE-2025-61927","record":{"aliases":["CLSA-2026-1789467187","CLSA-2026-1792254627","CLSA-2026-1792866960","GHSA-37j7-fg3j-429f"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Happy-DOM JavaScript library","requires_auth":"high_privilege","summary":"Happy-DOM allows VM context escape via JavaScript evaluation, enabling remote code execution on the host system.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:A/VC:L/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Happy-DOM has VM Context Escape","id":"CVE-2025-61927","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"Better Auth: Unauthenticated API key creation through api-key plugin","id":"CVE-2025-61928"},"packages":[{"ecosystem":"npm","fixed":["20.0.0"],"introduced":["0"],"last_affected":[],"package":"happy-dom","purl":null,"source":"GHSA-37j7-fg3j-429f"},{"ecosystem":"npm","fixed":["20.0.0"],"introduced":["0"],"last_affected":[],"package":"happy-dom","purl":"pkg:npm/happy-dom","source":"GHSA-37j7-fg3j-429f"}],"prev":{"headline":"Allstar Reviewbot has Authentication Bypass via Hard-coded Webhook Secret","id":"CVE-2025-61926"},"products":["happy-dom"],"published":"2025-10-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-10","vendors":["capricorn86"]},"summary":"Happy-DOM allows VM context escape via JavaScript evaluation, enabling remote code execution on the host system.","url":"https://insights.sbomify.com/CVE-2025-61927/"}