Skip to content
vulnerability

CVE-2025-54313

7.5
High
KEV · Exploited in wildEPSS 5%

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.

exploited
Yes, in CISA KEV since 22 Jan 2026fix by 12 Feb 2026 (CISA deadline for US federal agencies)unvetted proof-of-concept code on github
fix
No fixed release stated by the publisher
likelihood
EPSS 5.1%
Published 19 Jul 2025Analysed here 2 Nov 2026CVSS scored by the publisher (CNA)

do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

triage
supply chainruntime + configWAF can block: noAV · networkCWE-506· Embedded Malicious Code

Can a WAF block it? No. The vulnerability involves malicious code embedded in a package that executes during installation on Windows. This requires local installation and execution, not an HTTP request, so a web application firewall cannot block it.

Also consider: SBOM · artifact signing

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectornetworkattack complexityhighprivileges requirednoneuser interactionnonescopechangedconfidentialitylowintegrityhighavailabilitynone
CVSS 3.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N
common questions

Is CVE-2025-54313 being exploited?

Yes. CVE-2025-54313 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2025-54313?

CVE-2025-54313 is rated High with a CVSS score of 7.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-54313?

Not known from our data. No patch reference has been recorded for CVE-2025-54313, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2025-54313 affect?

CVE-2025-54313 affects prettier:eslint-config-prettier, prettier:eslint-plugin-prettier, un-ts:synckit, un-ts:pkgr\/core, and 3 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
prettier:eslint-config-prettierprettier:eslint-plugin-prettierun-ts:synckitun-ts:pkgr\/corealexghr:got-fetchun-ts:napi-postinstallhomarr:homarr
affected versions
prettier eslint-config-prettier
  • affected8.10.1
  • affected9.1.1
  • affected10.1.6
  • affected10.1.7

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

public exploits

Unvetted proof-of-concept code on GitHub: 2 GitHub proofs of concept

GitHub proofs of concept

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
no
technical impact
partial

Assessed by CISA 23 Jan 2026 (SSVC 2.0.3).

timeline

  1. 19 Jul 2025Published
  2. 26 Jul 2025First proof-of-concept repository on GitHub (unvetted) · 6 days later
  3. 22 Jan 2026Added to CISA KEV (exploited in the wild) · 180 days (about 6 months) later
  4. 23 Jan 2026CISA SSVC assessment: exploitation active · 1 day later
  5. 12 Feb 2026CISA remediation due date (US federal agencies) · 20 days later
  6. 26 Feb 2026CVE record last updated · 15 days later
  7. 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later

also known as

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
10 references in the CVE record: 10 links
Show 2 more
  • Linkendorlabs.com /learn/cve-2025-54313-eslint-config-prettier-compromise----high-severity-but-win
  • Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-54313

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA KEV catalog: exploitation, date added, due date
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • PoC-in-GitHub: GitHub repositories that claim a proof of concept
  • OSV: advisory aliases and downstream package versions
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved