Vulnerabilities
Known CVEs matched against the software your devices report, with severity, exploitation data, and affected devices.
Add-on required: Vulnerability matching needs the DIAM (Device Identity) add-on with the deviceTrust feature, available on the Advanced tier and above.
The software and operating-system versions your devices report are matched against a public vulnerability database. The Vulnerabilities page lists the CVEs that actually apply to your fleet, so the list is a work queue rather than a feed.
The list
Only CVEs with at least one match in your fleet are listed, newest publication first. Each entry shows its identifier, severity and publication date. Open one to see its full record.
What a CVE entry tells you
| Field | Meaning |
|---|---|
| Base score, Base severity | The CVSS score and its severity band. |
| CVSS vector | The scoring vector, with exploitability and impact sub-scores. |
| Score source | Who assigned the score, since different sources can rate the same CVE differently. |
| EPSS score | The probability of exploitation activity in the next 30 days, with the percentile it falls into. |
| Known exploited | The CVE is on the CISA catalog of exploited vulnerabilities, with the date it was added, the required action, and the due date. |
| Used for ransomware | The vulnerability is known to have been used in a ransomware campaign. |
| Published, Updated | When the record was published and last changed. |
| Matching devices | The devices in your fleet affected by it, with the product and version that matched. |
Prioritize by exploitation, not only by score. A medium-scored CVE that is on the known-exploited list and used in ransomware campaigns deserves attention before an unexploited critical one. The EPSS score and the exploited flag exist for exactly that judgment.
How a match is decided
A match is made against the vendor, product and version a device reports, including version ranges, so an entry states which versions are affected: from a version, up to and including a version, or before a version. Some vulnerability records only apply to a combination of products, and those matches note which other product had to be present.
Per-device view
Each device has its own Vulnerabilities tab in the device inventory that lists the CVEs matched for that machine. The fleet list answers "which vulnerabilities do we have", the device tab answers "what is wrong with this machine".
The result also feeds compliance: a device compliance policy can require that a product is not vulnerable, which turns a CVE match into a non-compliant device and, through conditional access, into a blocked sign-in.
Freshness
Matching runs in the background against the device's last reported software. Two timestamps matter when a result looks wrong:
- The device's last CVE check, shown on the device's System tab.
- The device's last seen time. A device that stopped reporting keeps its last known software list, so its CVE matches age with it.
A device that changed its software is re-checked on its next evaluation, not instantly.
Troubleshooting
- The page says the feature is not available in this edition. Vulnerability matching depends on a vulnerability data service that is not part of every edition. The rest of the device inventory keeps working.
- A CVE you expect is missing. Matching happens on what the device reports. Confirm the product and version appear in the software inventory; a product the client does not report cannot be matched.
- A CVE looks like a false positive. Check the affected version range on the CVE entry against the version the device reports. Vendors sometimes back-port fixes without changing the version string, which no version-based matching can detect.
See also
- Software inventory for the reported products the matching runs on.
- Device inventory for per-device vulnerabilities and posture.
- Policy violations for compliance failures, including the not-vulnerable check.