TL;DR: Coalition measured a larger vendor set, more contributing vulnerabilities, and a higher average vendor score in Q2 2026. Third-party exposure needs tighter review when exploitability, not just CVE volume, is moving the risk picture.
Editorial analysis by NHI Mgmt Group, based on content published by Coalition: “Risky Tech Ranking: Q2 2026 Updates”.
By the numbers:
- The Average Vendor Score increased 110% since Q2 2025.
Key questions
Q: Why does exploitability matter more than severity in CTEM prioritisation?
A: Severity alone does not show whether an attacker can reach the exposure or turn it into a compromise path.
Q: What are the signs that vendor and account risk is increasing in practice?
A: Common warning signs include unusual access times, abnormal data downloads or transfers, privilege escalation attempts, lateral movement patterns, exposed vendor credentials, and a drop in vendor security ratings.
Q: What should security teams do when an exploited CVE is tied to a third-party product?
A: Treat the issue as an operational assignment problem, not just a scanner finding.
Practitioner guidance
- Prioritise exploitability over raw CVE volume Use exploitability-weighted review to decide which vendors and products move to the front of patch, containment, and exception queues.
- Map risky products to identity and access dependencies Inventory which externally facing products sit on authentication, privilege, token, or administrative paths so a weakness can be tied to access exposure.
- Shorten remediation SLAs for products with rising exposure Set tighter internal deadlines when a product’s vulnerability count and exploitability profile both trend upward across consecutive quarters.
Bottom line: The core issue is not just how many flaws exist, but how quickly exploitable weaknesses change the risk profile of third-party technology.
Glossary terms: Exploitability-Weighted Risk, Application Exposure Drift, Third-Party Attack
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Exploitability-weighted ranking is more operationally useful than raw CVE counting. A vendor with fewer total vulnerabilities can still present a worse real-world risk if its issues are easier to exploit or more likely to be weaponised quickly. That is the right lesson from this ranking: remediation priority should follow exploitability and exposure path, not disclosure volume alone. Practitioners should use ranked exposure to decide where response SLAs tighten first.
A question worth separating out:
Q: How should organisations review third-party risk when a vendor’s ranking moves sharply?
A: Treat sharp movement as a trigger for governance review, not just a reporting note. Recheck exposure paths, renewal assumptions, and exception decisions, then decide whether the product deserves tighter controls, faster remediation, or reduced trust in sensitive workflows.
👉 Read our full editorial: Risky tech scores show exploit exposure is widening in 2026