Guides

How to prioritise dependency vulnerabilities

Updated 2026-11-17

Short answer

Fix first the dependency vulnerabilities that are being exploited and whose vulnerable code your application can actually reach. Then group the rest by package, because one update often closes many alerts.

Questions to ask about each alert

  1. Does it affect the exact version in my lock file?
  2. Is it in a direct dependency or a deep one?
  3. Does my code call the vulnerable function, and can that call be reached from outside?
  4. Is it being exploited? Check the CISA KEV list and the EPSS score.
  5. Is there a fixed version, and is the upgrade a patch or a major change?

Group by update, not by alert

Ten alerts on the same package are one piece of work. Order the list by which update removes the most risk.

Keep it from growing back

Scan on every pull request so a new vulnerable dependency is caught when it is added, and get alerted when a new vulnerability is published for something you already use.

More guides

Scan yours before the next merge.