CVE-2025-54313
HIGHCVE-2025-54313 is a high-severity (CVSS 7.5) CWE-506 vulnerability in eslint-config-prettier. O3 Security confirms whether CVE-2025-54313 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
eslint-config-prettier, eslint-plugin-prettier, synckit, @pkgr/core, napi-postinstall have embedded malicious code
Exploitation Status
Actively exploited in the wild
- CISA’s SSVC triage classifies this CVE as under active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-54313.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-54313 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 0 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
eslint-config-prettiernpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | eslint-config-prettier | ≥ 8.10.1&&< 8.10.2 | 8.10.2 |
| 📦npm | eslint-config-prettier | ≥ 9.1.1&&< 9.1.2 | 9.1.2 |
| 📦npm | eslint-config-prettier | ≥ 10.1.6&&< 10.1.8 | 10.1.8 |
| 📦npm | eslint-plugin-prettier | ≥ 4.2.2&&< 4.2.4 | 4.2.4 |
| 📦npm | synckit | ≥ 0.11.9&&< 0.11.10 | 0.11.10 |
| 📦npm | @pkgr/core | ≥ 0.2.8&&< 0.2.9 | 0.2.9 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for eslint-config-prettier. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update eslint-config-prettier to 8.10.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-54313 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2025-54313 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2025-54313. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-54313 in your dependencies?
O3 detects CVE-2025-54313 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.