Vulnerability Tracking
The Security page shows known vulnerabilities (CVEs) in the applications installed across your devices, which devices run a vulnerable version, and whether a catalog update can fix them.
In short
- Pckgr cross-references the apps detected on your devices with the National Vulnerability Database (NVD), refreshed daily.
- Only apps linked to a catalog entry are tracked; fix a wrong link from the vulnerable applications table.
- When the catalog has a fixed version, one button queues the update for every patchable device.
- Devices past the tenant's dormant threshold, and apps you dismiss, are left out of the counts.
- Both Security pages export to CSV, down to one row per device, app and CVE for an audit.
How it works
When devices check in, the Pckgr agent reports every application installed on the machine. Pckgr matches each detected app to its catalog entry, which is linked to one or more NVD product names (CPE identifiers). The installed version is then compared against published CVE ranges to determine whether the device is vulnerable.
- NVD sync
- CVE data is fetched from the NVD on a daily schedule.
- CPE matching
- Each catalog package is mapped to NVD vendor/product pairs so the right CVEs are associated. Pckgr maintains these mappings for you.
- Version evaluation
- For every detected app, the installed version is checked against each CVE’s affected version ranges.
- Rollup
- Per-device CVE counts are aggregated into the security overview and the dashboard alert.
The evaluation refreshes automatically after each NVD sync and whenever devices report updated inventory.
Devices that haven't checked in within the tenant's dormant threshold are excluded from all vulnerability counts, so long-offline machines don't inflate the numbers. When any are excluded, the overview shows how many.
Dashboard alert
When vulnerable devices exist, a security alert tile appears on the main dashboard showing:
- Number of devices with known vulnerabilities
- Critical CVE count (if any)
- Total open vulnerability instances
Click View Security to go to the full security page.
Email alerts
The Security alerts (weekly CVE digest) notification in Settings sends a weekly summary of open CVEs across your devices, plus an immediate alert when a new critical CVE is detected.
It only sends when at least one device is vulnerable, and goes to the tenant's notification recipients.
Security overview
The overview page has three metric cards at the top:
- Vulnerable devices
- Devices with at least one open CVE, out of total scanned.
- Critical CVE instances
- Total critical-severity CVE instances across all devices, highlighted red when above zero.
- Total open instances
- Sum of all open CVE instances across all vulnerable apps.
Below them, two charts summarise the vulnerable apps (dismissed apps are left out):
- Severity Distribution
- How many vulnerable apps have Critical, High, Medium or Low as their highest severity.
- Remediation Coverage
- How many vulnerable apps have a fix available in the catalog versus no fix yet, and the percentage Pckgr can patch.
Vulnerable applications table
Below the charts is a table of every application with known vulnerabilities in your tenant:
- Detected app
- The application name as reported by the device.
- Catalog match
- The catalog package this app is linked to. Click it to change it.
- Devices
- Number of affected devices.
- Critical
- Number of devices with critical CVEs for this app.
- Severity
- Highest CVE severity across all affected devices.
- Patchable
- Whether the catalog has a newer version that fixes at least one CVE.
Click a column header to sort by Detected app, Devices, Critical, Severity or Patchable. Two toggles sit above the table:
- Patchable only
- Show only apps where a catalog update fixes at least one vulnerability.
- Show dismissed
- Include apps you’ve previously marked as false positives.
Change a catalog match
If an app is linked to the wrong catalog package (for example, the wrong language or architecture variant), click the catalog match name to open the match picker.
Review the detected app and the candidates.
A dialog shows the detected app's details (name, publisher, version, architecture) and a list of candidate catalog packages ranked by match quality.Select a candidate and click Use this.
Or click Search catalog to find a package manually.Or click No catalog match to unlink the app entirely.
It will stop appearing on the security page.
Note
Dismiss an app
Click the eye icon on any row to dismiss it as a false positive. Dismissed apps are excluded from the dashboard alert and the metric totals. Use the Show dismissed toggle to view and restore them.
Export to CSV
On the Security page, select Export CSV.
The export covers the same devices as the page. Dismissed apps are included only while Show dismissed is on.Choose the Rows.
Pick one row per app for a summary, or one row per device, app and CVE for an audit.Select Export CSV.
The file downloads. Dates in it are UTC.
| Rows | What each row holds |
|---|---|
| One row per app | Every vulnerable app, not just those on screen: the detected app, catalog match, publisher, device counts, highest severity, whether the catalog has a fix, the catalog’s latest version and the IDs of its CVEs. |
| One row per device, app and CVE | Hostname, assigned name, last logged-on user, last seen, the app and installed version, the CVE with its severity and CVSS v3 score, and whether the catalog’s latest version fixes it. |
Note
App detail page
Click any row in the vulnerable applications table to see the detail page for that app.
Metrics
- Affected devices
- Devices running a vulnerable version.
- Critical exposure
- Devices with at least one critical CVE.
- Patchable by catalog
- Devices that can be patched by the current catalog version.
- Top severity
- Highest CVE severity across all affected devices.
Update every patchable device
If the catalog has a version that fixes vulnerabilities, an Update N devices button appears. Clicking it opens a confirmation dialog and then queues an update job for every patchable device. Devices with an in-flight job are automatically skipped.
Note
Devices table
- Device
- Device name (assigned name or hostname).
- Installed version
- The version currently installed on the device.
- Open CVEs
- Number of CVEs affecting this device’s installed version.
- Critical
- Number of critical CVEs.
- Fixed by catalog
- How many of those CVEs the catalog’s latest version resolves.
- Status
- “Update in progress”, “Patch available”, or no action needed.
Click any device row to open that device's detail page.
Select Export CSV to download one row per affected install: the device, its last logged-on user and last seen time, the installed version, its CVE counts and the IDs of the CVEs it has.
Device Security tab
Each device's detail page includes a Security tab showing vulnerabilities specific to that device.
Vulnerable apps list
Each catalog-linked app with open CVEs appears as an expandable card showing:
- App name, installed version, and publisher
- Total CVE count and critical count
- An Update to vX button when the catalog has a fix (with the number of CVEs it resolves), which queues the patch for that device directly
Click a card to expand it and see the individual CVEs.
CVE details
| Field | What it shows |
|---|---|
| CVE ID | Links to the NVD page for full details. |
| Severity | Critical, High, Medium, Low, or None. |
| Patch status | Fix in catalog, Fix published, No fix yet, or Patched. |
| Affected range | The version range this CVE applies to. |
| Recommended fix | The minimum version that resolves this CVE. |
| Published | When the CVE was published. |
| Description | Summary of the vulnerability. |
Coverage and limitations
- Coverage depends on detected apps being matched to a catalog entry whose NVD product names have been confirmed against the product's own version history. A product name that only looks right (a bundled component, or a product whose version numbers do not line up with the installed versions) is held back rather than counted.
- Apps without a catalog link are not tracked and don't appear here.
- CVE data is sourced from the NVD and refreshed daily. Zero-day vulnerabilities may not appear until they are published.
- Version comparison is best-effort for non-standard version schemes. Ambiguous versions are treated conservatively (not flagged as vulnerable).
- Vulnerability tracking currently covers Windows desktop applications only. Mobile and browser-extension CVEs are filtered out automatically.