Overview
This article explains how to view and configure the probability of a finding in Hyver — the estimated likelihood (as a percentage) that a vulnerability will be successfully exploited.
Hyver calculates this value automatically, but you can adjust it manually when needed to reflect your organization’s context or threat intelligence.
1. What probability means
The probability field reflects how likely it is that a threat actor could exploit the finding.
A higher probability usually means:
The vulnerability is well known in attacker communities
Tools or exploits are readily available
Very little skill or effort is required
This value is shown in the Mitigation Graph and used in overall risk scoring.
2. How Hyver calculates probability
Hyver uses four parameters:
Complexity – How difficult the exploit is (e.g., Very Easy to Hard)
Exploitability – Whether tools or exploits are available (e.g., Freely Available, Manual Only)
Popularity – How widespread the vulnerability is based on Hyver’s internal data
User Interaction – Whether the attack requires a user action (passive, active, or none)
Each value contributes independently to the final result:
Formula example:
Probability = Complexity × Exploitability × Popularity × User Interaction
For instance:
0.9 × 1 × 0.84 × 1 = 0.76 → 76%
This multiplicative approach ensures each factor’s impact is realistic — reflecting the idea that all conditions must align for an exploit to succeed.
3. How to edit a finding’s probability
Open the Findings list and select a row to view its details
Click the menu icon in the right pane and select Edit finding’s probability
From here, you can:
Use the Probability Calculator to adjust each of the four inputs via dropdown or manual entry (1%–100%)
Let Hyver recalculate the final value automatically
OR, if needed, toggle Override the auto calculator and enter your own custom value
Wrap-up / Next Steps
Fine-tuning the probability of a finding helps ensure risk scores reflect your organization’s real-world exposure. Use the built-in calculator when you want clarity — or override it when context demands a custom value.