Skip to Content

CVSS score calculation

VulnPilot displays a CVSS v4.0  score for vulnerabilities. That score is not always a raw publisher base score: VulnPilot normalizes metrics to CVSS v4.0, then enriches them with temporal (threat) and environmental information when it is available.

The CVSS score you see depends on where you are in the platform:

  • In the vulnerability catalog, the score is a base + temporal (threat) score.
  • In the monitor (and related action-plan views), the score is a base + temporal + environmental score personalized with your watchlist context.

Hover a CVSS badge to see the vector string used for the displayed score.

From older CVSS versions to CVSS v4.0

Whenever a native CVSS v4.0 vector is available, VulnPilot uses it.

When only an older score is published (CVSS 3.1 or 3.0), VulnPilot estimates an equivalent CVSS v4.0 base vector by mapping the v3 metrics to their v4 counterparts (attack vector, complexity, privileges, user interaction, CIA impacts, and subsequent impacts derived from scope). CVSS v2 is not converted.

The result is always evaluated as CVSS v4.0 for display and for BeeScore inputs.

Score composition

CVSS v4.0 combines several metric groups. VulnPilot uses them as follows:

Metric groupWhat it representsWhen VulnPilot applies it
BaseIntrinsic severity of the vulnerabilityAlways, when a score is available
Temporal / ThreatExploit maturity and related threat signalsCatalog and monitor, when exploitation information is available
EnvironmentalYour deployment and asset contextMonitor (personalized watchlist context)

In CVSS v4.0 terminology, the former temporal exploit metric is the threat metric (Exploit Maturity, E). VulnPilot still refers to it as temporal in product language because it plays the same role: adjusting severity based on how exploitable the issue currently is.

Temporal (threat) metrics

Temporal metrics are added when VulnPilot has exploitation signals, for example:

  • Active or known exploitation → Exploit Maturity Attacked
  • Proof of concept available → Exploit Maturity Proof-of-concept
  • No reported exploitation → Exploit Maturity Unreported

These signals come from vulnerability intelligence (tags, CISA ADP / KEV / SSVC enrichment, and similar sources). The catalog and the monitor both include temporal adjustments when that information exists.

Environmental metrics

Environmental metrics personalize the score to your context. They are applied in the monitor (and action-plan views tied to a watchlist). They come from two aspects of your watchlist configuration:

Watchlist sensitivity

How sensitive the watched assets are (their criticality in the watchlist) drives the CVSS security requirements:

  • Confidentiality Requirement (CR)
  • Integrity Requirement (IR)
  • Availability Requirement (AR)

Higher criticality raises those requirements and can increase the environmental score. Lower criticality lowers them.

Note

The watchlist sensitivity level (Low / Medium / High) used when creating or editing a watchlist mainly adjusts BeeScore prioritization thresholds (for example EPSS). The environmental CVSS adjustment described here comes from the criticality of the matched watchlist item.

Product exposure

Product exposure describes the network context in which the product is deployed. VulnPilot maps it to the CVSS Modified Attack Vector (MAV):

Product exposureModified Attack Vector
InternetNetwork
LocalNetworkAdjacent
RestrictedAdminNetworkAdjacent
LocalMachineLocal

This reflects that a vulnerability which is remotely exploitable in theory may be less severe for a product that only runs on a local machine or a restricted admin network.

Note

Product exposure is set on watchlist items (including via file import). Typical exposure tags on catalog products can also inform generic scoring outside a personalized monitor context.

Catalog vs monitor

Vulnerability catalog

On the catalog page, the displayed CVSS is the CVSS v4.0 base + temporal score for the vulnerability (often taken as the highest relevant product-specification score). Environmental personalization from your watchlists is not applied.

Monitor

On the monitor page, VulnPilot recomputes the score with your watchlist context:

  1. Start from the CVSS v4.0 base vector (native or converted).
  2. Apply temporal / threat metrics when exploitation information is available.
  3. Apply environmental metrics from watchlist item criticality (security requirements) and product exposure (modified attack vector).
  4. Compute the final CVSS v4.0 score used in the UI.

That personalized CVSS is also an input to the personalized BeeScore.

Severity labels

Displayed severity bands for CVSS scores are:

ScoreSeverity
0.0 – 3.9Low
4.0 – 6.9Medium
7.0 – 8.9High
9.0 – 10.0Critical

If no usable CVSS vector can be resolved, the platform shows N/A / Unknown.

Relationship to BeeScore

CVSS is one component of BeeScore. BeeScore also factors in exploitation likelihood (EPSS), qualitative context (for example national CERT alerts), and watchlist sensitivity thresholds. See BeeScore for the full prioritization model.

Last updated on

© 2026 Sentibee SAS.