# Vendor ratings such as VPR, TruRisk and the Nucleus Threat Rating are proprietary scores; publish their scale and method before ranking by them

SCORING SYSTEM, read 10 Nov 2026

**The short answer.** Tenable VPR, Qualys TruRisk and the Nucleus Threat Rating are vendor ratings, each described only on vendor pages. Tenable publishes a 0 to 10 scale. Qualys and Nucleus publish no numeric scale or method in the sources read on 2026-11-10. None can be recomputed from outside the vendor.

- **Maintained by:** Tenable (VPR), Qualys (TruRisk, QDS), Nucleus Security (Nucleus Threat Rating)
- **Scale:** VPR 0 to 10 (Tenable); TruRisk and QDS none found on 2026-11-10; Nucleus rating described as low to existential, no numeric scale found
- **Current version:** Not versioned in the pages read
- **Updated:** VPR nightly; Nucleus Threat Rating daily; TruRisk not stated in the pages read
- **Answers:** A vendor-specific view of exploitation likelihood or risk, from the vendor's own data

## How to read these

Each of these is the vendor's rating, produced from the vendor's own data and described on the vendor's own pages. This page labels every statement by who made it. A vendor rating can be useful, but it is a different category of evidence from CVSS, EPSS and KEV, whose specifications or data are public.

The test this site applies is plain: is the scale published, is the method published, and can the rating be recomputed or checked against public data. The table gives the result for the three ratings as of 2026-11-10.

Two of the three vendor pages describe the rating inside a larger platform product. TruRisk appears on both the VMDR and Enterprise TruRisk Management pages, and the Nucleus Threat Rating sits inside Nucleus Insights. A rating that is part of a platform is usually available only through that platform, which limits an outside check.

| Rating | Scale published | Method published | Vendor claim read |
| --- | --- | --- | --- |
| Tenable VPR | Yes: 0 to 10 | Described as machine learning and real-world exploit data; no formula or feature list found | Recalculated nightly across 280,000+ vulnerabilities |
| Qualys TruRisk and QDS | None found on 2026-11-10 | None found; page cites 25+ real-time threat intelligence sources | TruRisk used to prioritize vulnerabilities exploited by ransomware; QDS filter offered |
| Nucleus Threat Rating | None found; described as low to existential | None found | Refreshed daily for every CVE |

## Tenable VPR

Tenable's capability page states that VPR gives each vulnerability a priority rating on a scale from 0 to 10 and calculates prioritization nightly for more than 280,000 distinct vulnerabilities. Tenable says VPR uses machine learning and real-world exploit data, and that it tested VPR against CVSS, EPSS and CISA KEV.

Tenable also states that VPR reduces the volume of CVEs requiring action from about 160,000 (CVSS-based) to about 4,000 (VPR-based) while maintaining strong exploit coverage. That is Tenable's claim. The page read gives no definition of coverage, no date range and no data set, so the ledger cannot test it. A reader can ask Tenable for the denominator and the window.

Cite the Tenable page with its read date of 2026-11-10, because a vendor can change a claim, a count or a scale without a version number, and a saved copy is the only proof of what was said on a given day.

The Tenable page presents CVSS, EPSS and KEV as comparators for VPR. That is a useful framing for a buyer, because it names the public benchmarks. The ledger supplies the same benchmarks over one year of KEV listings, so the question to put to the vendor is how VPR performed on the 318 CVEs on the date each was added.

## Qualys TruRisk and QDS

Qualys's VMDR page states that VMDR measures risk with TruRisk using 25 or more sources of real-time threat intelligence, prioritizes vulnerabilities exploited in the wild by ransomware using TruRisk and MITRE ATT&CK, and offers a filter on the Qualys Detection Score (QDS). The Enterprise TruRisk Management page adds a TruLens layer that correlates 25+ threat feeds and TruConfirm, an exploit validation capability covering 1,800+ CVEs, by Qualys's count.

In the pages read, Qualys states no numeric scale and no formula for TruRisk or QDS. That is recorded as none found on 2026-11-10, not as proof that none exists elsewhere in Qualys documentation.

Qualys's claims of 25+ sources and 1,800+ CVEs are counts, not performance measures. A count of feeds says how much input there is; it says nothing about how well the rating separates exploited from unexploited vulnerabilities.

## Nucleus Threat Rating

Nucleus states on its Insights page that the Nucleus Threat Rating is refreshed daily and is an exploitation-centric risk signal for every CVE, and describes it as a defensible rating from low to existential. The page gives no numeric scale and no method.

Nucleus also published a white paper claiming that between October 2025 and March 2026 its research reviewed every new KEV addition and found that 22 vulnerabilities, 18 percent, showed meaningful exploitation or exploitability signals before formal listing. The window ends 2026-03 and the ledger runs 2025-11-10 to 2026-11-09, so the two overlap only in part. That claim is the vendor's and has not yet been checked against CISA's catalog on this site.

## What the ledger can and cannot say

The KEV Lag Ledger can show what public signals did on listing day: median EPSS 0.0066, 75.8 percent of 260 below 0.1, 10.4 percent of 318 with CVSS below 7. Those are the benchmarks a vendor rating has to beat, and the ledger lists every row so a vendor can be tested on the same 318 CVEs.

It cannot score a proprietary rating, because the rating is not public per CVE. A buyer can ask each vendor for its per-CVE rating on the ledger's CVE list as of each dateAdded, and compare. The ledger data is on this site for that purpose.

Where a vendor rating is used in a federal context, the binding references remain public. BOD 26-04 names KEV status, exploit automation and technical impact, all of which are public data fields.

## Audit practice

Treat a vendor rating as one input, record its name, and keep the public inputs next to it. If a ranking mixes a vendor rating with CVSS, EPSS and KEV, the auditor's question is which input decided the order for each item. A rating whose scale is unpublished cannot answer that, so keep KEV and a documented EPSS threshold as the backstop.

Do not describe a vendor rating in a policy as an industry standard. State the vendor, the product, the date of the rating and the export used.

Some programs allow a vendor rating to override the public order. If yours does, write the override rule and review it against the public signals every quarter.

## Comparisons with this system

- [KEV vs vendor intelligence](/compare/kev-vs-vendor-intelligence/)
- [CVSS vs EPSS vs KEV](/compare/cvss-vs-epss-vs-kev/)

## Sources

- Tenable, Vulnerability Priority Rating: https://www.tenable.com/capabilities/vulnerability-priority-rating (read 10 Nov 2026)
- Qualys, VMDR (TruRisk, QDS): https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026)
- Qualys, Enterprise TruRisk Management (TruLens, TruConfirm): https://www.qualys.com/apps/enterprise-trurisk-management (read 10 Nov 2026)
- Nucleus Security, Nucleus Insights (Nucleus Threat Rating): https://nucleussec.com/platform/nucleus-insights/ (read 10 Nov 2026)
- FIRST, EPSS (public benchmark): https://www.first.org/epss/ (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://epssvscvss.com/scores/vendor-priority-ratings/
