Known exploited vulnerability
CVE-2025-54313
The short answer
CVE-2025-54313 affects prettier eslint-config-prettier and is rated high (CVSS 7.5). CISA added it to the Known Exploited Vulnerabilities catalog on 2026-01-22: attackers are using it, so patch it first. Fixed versions are published for eslint-config-prettier (8.10.2, 9.1.2, 10.1.8) and eslint-plugin-prettier (4.2.4).
What it is
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.
Weakness: CWE-506.
Severity
7.5 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N
Exploited (CISA KEV)
Yes, since Jan 22, 2026
Federal due date Feb 12, 2026
EPSS, next 30 days
5.1%
Higher than 92% of scored CVEs
How it can be exploited
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- High
- Availability impact
- None
What CISA says to do
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Affected packages and fixed versions
| Package | Ecosystem | Fixed in | Advisory |
|---|---|---|---|
| eslint-config-prettier | npm | 8.10.2, 9.1.2, 10.1.8 | GHSA-f29h-pxvx-f335 |
| eslint-plugin-prettier | npm | 4.2.4 | GHSA-f29h-pxvx-f335 |
| synckit | npm | 0.11.10 | GHSA-f29h-pxvx-f335 |
| @pkgr/core | npm | 0.2.9 | GHSA-f29h-pxvx-f335 |
| napi-postinstall | npm | 0.3.2 | GHSA-f29h-pxvx-f335 |
| got-fetch | npm | 6.0.0 | GHSA-f29h-pxvx-f335 |
Is it in your code? Drop your lockfile into the free vulnerability check, or let vulnerability watch check your repository every day and open the upgrade as a pull request.
Affected products
eslint-config-prettier. NVD's record lists the exact affected versions.
References
- github.com/prettier/eslint-config-prettier/issues/339 Issue Tracking
- news.ycombinator.com/item?id=44608811 Issue Tracking
- news.ycombinator.com/item?id=44609732 Issue Tracking
- socket.dev/blog/npm-phishing-campaign-leads-to-prettier-tooling-packages-compromise Third Party Advisory
- www.bleepingcomputer.com/news/security/popular-npm-linter-packages-hijacked-via-phishing-to-drop-malware/ ExploitThird Party Advisory
- www.npmjs.com/package/eslint-config-prettier?activeTab=versions Product
- www.stepsecurity.io/blog/supply-chain-security-alert-eslint-config-prettier-package-shows-signs-of-compromise ExploitThird Party Advisory
- github.com/community-scripts/ProxmoxVE/discussions/6115 Third Party Advisory
- www.endorlabs.com/learn/cve-2025-54313-eslint-config-prettier-compromise----high-severity-but-windows-only Third Party Advisory
- www.bleepingcomputer.com/news/security/popular-npm-linter-packages-hijacked-via-phishing-to-drop-malware/ ExploitThird Party Advisory
- www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-54313 US Government Resource
Questions
Is CVE-2025-54313 being exploited?
Yes. CISA added CVE-2025-54313 to its Known Exploited Vulnerabilities catalog on 2026-01-22, with a federal remediation due date of 2026-02-12.
How do I fix CVE-2025-54313?
Upgrade to a fixed version: eslint-config-prettier (npm) 8.10.2 or 9.1.2 or 10.1.8; eslint-plugin-prettier (npm) 4.2.4; synckit (npm) 0.11.10; @pkgr/core (npm) 0.2.9. CISA's required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
From NVD, CISA KEV, FIRST EPSS and OSV.dev, checked . Status on NVD: Analyzed. The description is NVD's text, quoted as published.
Related
Latest CVEs this week
Critical and High CVEs from the last 7 days, with KEV and EPSS.
Exploited vulnerabilities by vendor
Every vendor in CISA's KEV catalog, with its count.
Prettier exploited vulnerabilities
Everything CISA lists as exploited for Prettier.
Vulnerability watch
A briefing and a fix pull request when an advisory hits your dependencies.
Know the day a CVE lands in your code
Connect a GitHub repository and ZeusQA checks its dependencies daily, briefs each advisory and opens the fix. Three test runs free, no card.