Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:NSummary
CVE-2025-54313 is a high-severity Embedded Malicious Code (CWE-506) vulnerability in Microsoft Windows. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Embedded Payloads (T1027.009); ranked in the top 10% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SC-44 (Detonation Chambers) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
eslint-config-prettier versions 8.10.1, 9.1.1, 10.1.6, and 10.1.7 contain embedded malicious code as part of a supply chain compromise. The affected component is the npm package itself; installation triggers execution of an install.js script that drops and launches the node-gyp.dll malware on Windows systems. The vulnerability carries a CVSS 7.5 score reflecting network attack vector, high complexity, and impacts primarily to integrity with limited confidentiality effects under CWE-506.
An attacker who publishes or substitutes the malicious package versions can achieve code execution on any system that installs or updates to those releases. No authentication or user interaction beyond a standard package installation is required, allowing the malware to run in the context of the installing user on Windows.
Public references including the package repository issue, Socket.dev analysis, and BleepingComputer reporting describe the incident as resulting from a phishing campaign that compromised maintainer credentials for multiple Prettier-related tooling packages. The EPSS score rose from a low baseline to a peak of 0.1467, indicating emerging exploitation interest after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-21972
Vulnerability Data
eslint-config-prettier 8.10.1, 9.1.1, 10.1.6, and 10.1.7 has embedded malicious code for a supply chain compromise. Installing an affected package executes an install.js file that launches the node-gyp.dll malware on Windows.
- CWE(s)
- KEV Date Added
- 22 January 2026
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 3 hardening rules · 2 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover embedded malicious code before release.
Detonation chambers can reveal embedded malicious code through controlled execution analysis.
Integrity verification tools directly detect unauthorized or malicious code insertions.
Tamper-resistance and detection mechanisms identify malicious code introduced via the supply chain.
Component authenticity requirements reduce the chance malicious code is embedded by developers or suppliers.
Component authenticity controls stop introduction of malicious or counterfeit code into the product.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Assessing authenticity and integrity before acquisition catches embedded malicious code.
Secure SDLC practices directly prevent introduction of malicious code during development.
Due diligence prior to supplier relationships helps avoid sources of embedded malicious code.
Supplier risk assessment reduces likelihood of receiving products containing malicious code.
Pre-acquisition assessment of critical suppliers mitigates risk of malicious code in procured software.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Requiring suppliers to furnish component lists, attestations, and cryptographic verification of delivered artefacts makes it harder for an attacker to embed hidden malicious code that would otherwise go undetected through the supply chain.
Checks that executed code has not been tampered with and monitoring for malware-associated activity reduce the likelihood that hidden malicious code remains active.
Banning unapproved or unknown software and requiring testing plus authorization reduces the chance that hidden malicious code will be introduced into production environments.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 9 (1 rule)
- V-271452 OL 9 must use a Linux Security Module configured to enforce limits on system services. prevents CWE-506
RHEL 9 (1 rule)
- V-258078 RHEL 9 must use a Linux Security Module configured to enforce limits on system services. prevents CWE-506