Vulnerabilities
The Vulnerabilities screen (operations group in the sidebar) lists the CVEs and EUVDs detected in the environment, enriched with EPSS and with CISA's KEV catalogue, in priority order. It is available when the vulnerability watch module is turned on. The SUPER_ADMIN, ADMIN, MANAGER, USER and AUDITOR roles can view it.
Vulnerabilities arrive through the Wazuh, EterScan and OpenCTI integrations and through the public EUVD and NVD feeds.
What it shows
The cards at the top show: Open, Exploited (KEV), EPSS ≥ 10%, Overdue and Median time to fix. You can filter by Open / Closed / All, by severity, KEV only, EPSS ≥ 10%, Overdue and Not applicable, or search by CVE, EUVD or title.
| Column | What it means |
|---|---|
| CVSS | Technical severity of the vulnerability |
| EPSS | Probability of exploitation in the next 30 days (FIRST EPSS). If the source does not provide it, "No EPSS score" appears |
| KEV | Listed in CISA's catalogue of actively exploited vulnerabilities |
| Priority | From 0 to 100, combines CVSS (35), EPSS (30), KEV (20) and asset criticality (15). It is the order in which you should handle vulnerabilities |
| Fix deadline | Counted from detection; shows "N days left" or "N days overdue" |
| Status | Open, Being fixed, Fixed, Risk accepted, False positive or Not applicable |
Fix deadlines by severity
The deadline is counted from the detection date:
| Situation | Deadline |
|---|---|
| Listed in the KEV catalogue | 14 days |
| Critical | 15 days |
| High | 30 days |
| Medium | 90 days |
| Low or informational | 180 days |
| No severity | 90 days |
When a vulnerability has both KEV and a severity, the shorter deadline applies. The Overdue card uses these deadlines. Vulnerabilities that already existed without a deadline receive one automatically.
What affects me?
The public feeds bring thousands of CVEs that have nothing to do with your organisation. The What affects me? button cross-references the open CVEs from those feeds (NVD and EUVD) with what EterShield knows about the environment (Wazuh and EterScan detections, agent packages, device operating systems, assets, SBOM components and vendors) and separates them into three groups:
- Affect: detected in the environment or linked to an asset.
- Possible: the vendor or product matches the inventory. They stay open for you to decide one by one.
- Do not apply: no sign in the environment.
Nothing changes until you confirm. To clear them, click Mark N as "not applicable". If any of the ones that do not apply is in the KEV catalogue, the screen warns you and shows the first ones to confirm: confirm that the product does not exist in the organisation. Those marked stay under the Not applicable filter and stop counting as open. Without an inventory or detections, there is no way to know what does not apply (connect Wazuh or register devices, assets or components). Firewalls, routers and VPNs are rarely in the inventory: register them as assets with the brand in the name.
The feeds no longer create "not applicable" rows: only relevant CVEs come in.
Marking as not applicable or changing the status
Open the vulnerability and choose the new status (for example, Being fixed, Fixed, Risk accepted, False positive or Not applicable). Who can update the status: SUPER_ADMIN, ADMIN and MANAGER. Other roles can only view. The record also shows the affected assets and the publication, detection and fix dates.