How to Find and Fix CVEs Across Every Client Machine

What's in the demo

• Four tiles per client: open criticals, known-exploited (CISA KEV) exposure, findings with a patch ready, accepted risks about to expire
• Findings grouped by the software you'd fix (Chrome, Firefox, 7-Zip), each with a risk score built from CVSS severity, EPSS exploit probability, and KEV status
• The Chrome drawer: three CVEs across two machines, with CVSS, EPSS percentage, and KEV badge per CVE
• Remediate: queue the approved Chrome update against one workstation's three findings, straight from the finding
• Accept risk on 7-Zip with an expiry date and a note; the finding reopens on its own when the date passes
• Create a ticket for the Firefox finding, pre-filled with the CVE details and linked back to it
• Switch to the By CVE view to answer "are we exposed to this one?" across every machine a client owns

Questions this video answers

Do I need a separate vulnerability scanner with Breeze RMM?

No. Breeze matches the software inventory its agent already collects against the National Vulnerability Database, so there is no extra agent or subscription.

How does Breeze RMM prioritize vulnerabilities?

It groups findings by software and scores each group on CVSS severity, EPSS exploit probability, and whether the CVE is on CISA's Known Exploited Vulnerabilities list.

Can I patch a CVE directly from the vulnerability finding?

Yes. If the update is approved in Breeze patch management, Remediate queues the install against the findings on the devices you select.

What happens when I accept a vulnerability risk in Breeze?

You set an expiry date and a reason. When the date passes the finding reopens automatically, and the "Accepted, expiring soon" tile shows what is coming due.

Can I check whether a client is exposed to a specific CVE?

Yes. Switch the board to By CVE and search for it to see every affected machine for that client.