Pricing Insights
Book a demo

A critical CVE in a library: update, replace or accept the risk

SCA reported a critical vulnerability in a dependency. Below is the decision order in one review: whether it affects you, how urgent it is, and which of four options to choose.

Points for banks: ARDFM No. 53 review · official text on adilet.zan.kz

Checklist

  • The version from the lock file is checked against the vulnerable range; it is clear whether the dependency is direct or transitive
  • Affected applications found through the SBOM
  • Urgency assessed by KEV, EPSS and whether the service is reachable from the internet, not by CVSS alone
  • Updated to the fixed version, repeat SCA scan is clean
  • If there is no fix: compensating measures and a review date
  • If the risk is accepted: in writing, who, why, which measures, when to review

1. Does it affect you

SCA reported a critical CVE. The first question is whether you really have the vulnerable version and where it came from.

  • Does the library version fall into the vulnerable range from the bulletin? Check against the lock file, not the manifest: package.json may say ^1.2.0 while 1.4.7 is installed.
  • Is it a direct or a transitive dependency (another library pulled it in)? How you update depends on this.
  • Where is the library used: in production code, only in tests, or in build tools?
  • How many applications are affected: the SBOM answers this in minutes, with no searching across repositories.

2. How urgent is it

CVSS says how bad it can be, but not how likely it is. Three questions determine urgency.

  • Is the vulnerability exploited in attacks, is it in the CISA KEV catalog? If yes, it is no longer theory.
  • How likely is exploitation in the near future: the EPSS score.
  • Is the vulnerable service reachable from the internet and is the vulnerable code reachable: is the vulnerable function called, under which settings is it dangerous.
  • Exploited and reachable from the internet: fix within hours and days. Critical but unreachable: put it in the planned cycle with a note on why.

3. Update: the first option

In most cases the right answer is to update to the fixed version. The only question is how to do it without breaking anything.

  • If the fix is in the same major version, update: the risk of breakage is minimal and ordinary tests are enough.
  • If the fix is only in a new major version, plan a migration and use the compensating measures from step 5 in the meantime.
  • Transitive dependency: update the parent library or force the version: overrides in npm, resolutions in Yarn, dependencyManagement in Maven, constraints in Gradle and pip.
  • After updating, run a repeat SCA scan and tests to make sure the vulnerable version has not come back through another dependency.

4. Replace: if the library is abandoned

If there is no fix and there will be none, there is nothing to update to. The signs of an abandoned library are visible in advance.

  • The last release was more than a year ago, issues and pull requests go unanswered.
  • A single maintainer who does not respond is also a risk of account takeover and a malicious version.
  • Look for a maintained alternative or a fork that accepted the fix; sometimes a small function is easier to rewrite yourself.
  • Block the replaced library in the proxy repository so it does not return in another project.

5. Compensate: while there is no fix

When you cannot update right now, reduce the risk another way, and set a date to come back to it.

  • Turn off the vulnerable feature or setting if you can live without it.
  • Close access to the vulnerable service from the internet or limit it to a list of addresses.
  • A WAF rule for the specific exploit, a “virtual patch”. This is a temporary measure: the hole in the code remains.
  • Strengthen monitoring: logs for the signs of exploitation from the bulletin.

6. Accept the risk: deliberately and on record

Sometimes a vulnerability is really not dangerous for you: the code is unreachable, the feature is not used, the service is isolated. Then the risk can be accepted, but only in writing.

  • Who made the decision and who approved it on the security side.
  • Why the vulnerability is not dangerous, specifically: “function X is not called”, not “we have an internal network”.
  • Which compensating measures are in place.
  • Review date: the decision is reviewed on new information, for example if the vulnerability enters KEV.
  • In SCA, the status “not affected” with a reason, so the finding does not return in every scan (for exchange with others, the VEX format).

For banks: what ARDFM No. 53 says

For banks the deadlines and procedure are partly set by the regulator: library analysis is mandatory, critical vulnerabilities in remote service software are fixed before release, critical updates no later than one month.

clause 150Analysis of components and (or) third-party libraries ... is carried out to identify known vulnerabilities inherent in the version of the component and (or) third-party library in use, and to track dependencies between components and (or) third-party libraries and their versions.editors' translation
clause 151The bank or organization ensures corrective measures to eliminate the identified vulnerabilities in the manner defined by an internal document approved by the executive body. Critical vulnerabilities are eliminated before commissioning of the remote service software and (or) its new versions.editors' translation
clause 121Security updates of information assets that eliminate critical vulnerabilities are installed no later than one month from the date of their publication and distribution by the vendor, except for cases agreed with the information security unit.editors' translation

To make it easier next time

Reaction speed to a new CVE is determined by what was done before it.

  • Lock files in the repository, so it is always clear which version is installed.
  • SCA on every build, not once a quarter, and an SBOM for every release.
  • A package proxy repository: you can block a vulnerable or malicious version for all projects at once.
  • Automatic updates (Renovate, Dependabot): small updates every week are easier than one big one a year.
  • Follow exploited vulnerabilities, for example with the TRAIO Insights CVE radar.

Questions and answers

What if there is no fixed version of the library?

Compensating measures: turn off the vulnerable feature, limit access to the service, a temporary WAF rule, stronger monitoring. In parallel, look for a replacement if the library is abandoned.

How do I update a transitive dependency?

Update the library that pulls it in, or force the version: overrides in npm, resolutions in Yarn, dependencyManagement in Maven, constraints in Gradle and pip. Then scan again.

Can a critical CVE be left unfixed?

You can accept the risk if the vulnerability is unreachable or not dangerous in your configuration: in writing, with security approval, compensating measures and a review date. For banks, critical vulnerabilities in remote service software are eliminated before commissioning (ARDFM No. 53, clause 151).

Why not rely on CVSS alone?

CVSS rates severity, not likelihood. Most vulnerabilities rated critical by CVSS are never exploited, and some exploited ones score below 9. Add KEV, EPSS and the exposure of the service.