What’s Included
Each vulnerability report includes: Per-CVE status:| Status | Meaning |
|---|---|
| Fixed | Root has applied a patch; the CVE is no longer exploitable |
| Under SLA | Root is actively working on a patch within the committed SLA |
| No Fix Available | No upstream fix exists yet; Root is monitoring |
| Not Affected (VEX) | The CVE exists in a dependency but is not exploitable in this artifact |
- CVE ID (e.g.,
CVE-2024-1234) - Severity: Critical, High, Medium, Low
- CVSS score
- Package name, version, and ecosystem (PyPI, APK, APT, npm, Maven)
- OS distro and release
- Number of affected assets in your environment
- SLA deadline (for CVEs under active remediation)
- Date patched (for fixed CVEs)
Report Format
Web UI: The Vulnerabilities page displays an interactive table with all CVEs across your subscribed artifacts. Columns include CVE ID, ecosystem, package, version, OS distro, affected asset count, severity, CVSS score, and SLA status. CSV export: Download the current report as a CSV file from the Vulnerabilities page. The export includes all columns visible in the table and reflects your active filters. JSON (API): The API returns structured JSON with the same fields, suitable for ingestion into SIEM, ASPM, or ticketing systems.Accessing Reports
Via the Root platform UI:- Navigate to Vulnerabilities in the sidebar
- View CVEs grouped by status: Fixed, Under SLA, No Fix Available
- Use the search bar to find a specific CVE ID
- Click any CVE to see which images and packages are affected
Filtering and Scoping
In the UI, filter by:- Package name - find all CVEs in a specific library
- Ecosystem - narrow to PyPI, APK, APT, npm, Maven
- Severity - Critical, High, Medium, Low, Unknown
- SLA status - Met, Active (under SLA), Breached, Not Applicable
- Fix status - Fixed, Not Fixed