Vulnerabilities: detect and remediate security flaws across your fleet

Overview

The Vulnerabilities feature lists the known security flaws (CVEs) present on the machines in your fleet, based on the software they have installed. A single screen shows which applications expose your customers, at what level of risk, and on which agents.

It answers three questions:

  • Which CVEs affect my fleet? Each vulnerability is identified by its CVE number, description and CVSS score.
  • Which applications should I update first? Each application is ranked by number of CVEs and highest CVSS score.
  • Which machines are affected? For each CVE or application, you get the list of impacted agents, which you can export.

The data comes from the public reference databases: the CVE Program and NIST's National Vulnerability Database (NVD). RG System matches these databases against your agents' software inventory and, for Windows, against pending updates.

Requirements

Item Condition
Activation The Vulnerabilities feature must be enabled on your account. Otherwise, the menu entry does not appear. Contact your RG System representative.
Supported agents Windows agents, Server or Workstation.
Software inventory The agent must report its software inventory: it is used to detect vulnerable applications.
CVE scope CVEs published since 2015 and linked to an identified product (CPE) in the NVD.

Vulnerabilities are not computed in real time: a regular scan updates the results. The date of the last scan is shown at the top of the screen (for example "Last scan performed on April 13, 2026 at 13:35").

Accessing the feature

Open the screen from the Cybersecurity > Vulnerabilities menu. 

6.png

What it shows depends on the item selected in the tree:

  1. On a customer or a node: you see the vulnerabilities of every machine below it, with the number of impacted agents.
  2. On a Windows agent (Server or Workstation): you see only that machine's vulnerabilities. The "Impacted agents" indicators and columns are hidden, since only one agent is involved.
7.png

Understanding the screen

The screen is made of an overview and a list, available from two angles: by CVE or by application. The overview follows the filters applied to the list.

Overview

  • Breakdown by CVSS score: number of CVEs with a low, medium and high score.
  • Vulnerable applications: number of distinct applications affected.
  • Vulnerable machines: number of distinct agents affected (hidden at agent level).
  • Top 5 most critical CVEs or applications.
8.png

By CVE tab

One row per vulnerability, sortable by score and by number of impacted agents.

Column Content
CVE Id Official identifier, for example CVE-2026-4439
CVSS score Severity from 0 to 10 (most recent CVSS version available: 4.0, otherwise 3.x, otherwise 2.0)
Impacted agents Number of exposed machines
Description Summary of the flaw published in the CVE database
9.png

By application tab

One row per application and version, sortable by number of CVEs, highest score and impacted agents.

Column Content
Application Software name, for example Microsoft Edge
Version Version installed on the agents
Publisher Software publisher
CVE count Known vulnerabilities for this version
Max CVSS score Score of the most severe CVE for this version
Impacted agents Number of machines where this version is installed
10.png

Searching and filtering

Filters apply to the CVSS score, the number of impacted agents and, in the By application tab, to the name, version, publisher and CVE count. Text search matches whole words: type Firefox rather than fire.

Handling a vulnerability

Remediation follows four steps: prioritize, analyze, fix, verify.

  1. Prioritize. In the By application tab, sort by Max CVSS score, then by Impacted agents. Applications at the top of the list are the ones to fix first.
  2. Analyze. Click the wrench icon on a row to open the detail panel:
    • from an application: its list of CVEs, with score and description;
    • from a CVE: its full description and the affected applications;
    • the Impacted agent(s) tab: name, ID, path in the tree and type of each exposed machine.
  3. Fix. Update the application to a non-vulnerable version with App Manager, or deploy pending Windows patches with Windows Update.
  4. Verify. After the next scan (see the last scan date), the fixed version disappears from the list. Removing a software can take up to two scan cycles to be reflected.

Exporting

The export button produces a file of the displayed list, with the current filters. Two exports are available:

  • Vulnerability list: columns of the active tab (By CVE or By application).
  • Impacted agents: from the detail panel, the list of exposed machines (Agent Name, Agent Id, Agent path, Agent Type).

Export column headers are in English. The file is generated in the background, then made available like other platform exports.

FAQ

Why does the same application appear several times?
Each installed version is a separate row: CVEs depend on the version. Filter by application name to group them.

I updated a software, but it still appears.
Results reflect the last scan, shown at the top of the screen. Wait for the next cycle.

I don't see the Vulnerabilities entry in the menu.
The selected agent is not a Windows agent.

A CVE looks like a false positive.
Detection relies on matching the software name and version against the NVD. Some software is poorly identified in that database. Report the case to support with the CVE ID, the software and its version.

Are Microsoft Store applications (Teams, for example) scanned?
Not yet.