CVE Tools

CVE-2025-54313

Exploited in the wild. In CISA KEV since 2026‑01‑22. Fixed versions are out.

Published Updated Sources: CVE.org, NVD, GitHub, BDU

What to do

Find your product and version, then upgrade to the build on the right.

  • Npm Eslint-config-prettierAffected: ≥ 8.10.1, < 8.10.2Upgrade to: 8.10.2Stated by: GitHub advisory
  • Npm Eslint-plugin-prettierAffected: ≥ 4.2.2, < 4.2.4Upgrade to: 4.2.4Stated by: GitHub advisory
  • Npm SynckitAffected: ≥ 0.11.9, < 0.11.10Upgrade to: 0.11.10Stated by: GitHub advisory
  • Npm @pkgr/coreAffected: ≥ 0.2.8, < 0.2.9Upgrade to: 0.2.9Stated by: GitHub advisory
  • Npm Napi-postinstallAffected: ≥ 0.3.1, < 0.3.2Upgrade to: 0.3.2Stated by: GitHub advisory

Versions as the sources state them. 3 more products have version data. Full version matrix after sign-in

Coverage timeline

1 publisher
  1. AI code assistants may introduce security risks by recommending outdated or vulnerable packages without user verification.

  2. Added to CISA KEV catalog

    ·CISA KEV

Sourced from public security reporting — each date is when it was published, not when it happened.

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS92nd
CISA KEV
CISA KEV

Listed as exploited in the wild since 2026-01-22.

US federal agencies must remediate by 2026-02-12.

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

No public exploit or proof of concept found in the sources we track.

EPSS

5.1% chance of exploitation activity in the next 30 days, which ranks it in the 92nd percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Attention now

Sustained.

Lifecycle

8 events over 341 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. EPSS band changemoderate → low
  3. EPSS band changelow → moderate
  4. Patch availablerecord updated
  5. Added to CISA KEV
  6. Publishedweakness classified

Affected products

Technical detail

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N

Scored 7.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality LowSome restricted information is disclosed, but limited in scope
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability NoneNo availability impact

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Eslint-config-prettier, not every advisory. This one: actively exploited.