TL;DR: Exploit signals now matter more than raw counts, because Flashpoint says AI-assisted discovery pushed 21,667 vulnerabilities into the first half of 2026, with 20% carrying public exploit code and some weaponized within 24 hours. Prioritisation now has to follow exploitability, exposure and business context so remediation tracks likely attack paths.
Editorial analysis by NHI Mgmt Group, based on content published by Flashpoint: “The Flashpoint Method For Threat-Informed Vulnerability Prioritization”.
By the numbers:
- Nearly one-fifth, or 20%, of all vulnerabilities disclosed had publicly available exploit code.
- Some vulnerabilities are weaponized in as little as 24 hours after disclosure.
- Flashpoint’s Known Exploited Vulnerabilities list recently surpassed 7,000 entries, around 800 of which lack a CVE ID.
Key questions
Q: What breaks when vulnerability management is based only on CVSS scores?
A: CVSS-only prioritisation breaks when several lower-scoring flaws can be combined into a complete exploit path.
Q: What are the signs that OT vulnerability triage is failing?
A: Common signs include long lists of critical findings with no remediation order, repeated arguments between security and operations, and tickets that omit asset role or production impact.
Q: How should security teams prioritise vulnerabilities when AI speeds up attack discovery?
A: They should prioritise by exploitable context, not by severity alone.
Practitioner guidance
- Build a threat-informed triage model Score vulnerabilities using exploit availability, active exploitation, asset exposure, business criticality and remediation cost rather than severity alone.
- Map vulnerable assets to business services Tag internet-facing systems, privileged workflows and identity-dependent services so triage can reflect blast radius instead of scanner volume.
- Track exploitation signals as first-class inputs Treat KEV inclusion, public exploit code, zero-day status and threat chatter as operational triggers for escalation.
Bottom line: AI-assisted discovery increases vulnerability volume, but that alone does not tell security teams which flaws are most dangerous in context.
Glossary terms: Threat-Informed Vulnerability Prioritization, Exploitability signal, Exposure management, Prioritisation Debt
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Threat-informed prioritisation is now a governance requirement, not a tuning exercise. Vulnerability management has moved beyond counting findings and into deciding which exposures deserve scarce remediation capacity. Static severity scores cannot reflect exploit availability, asset criticality or business context, so programmes that still treat all high-severity findings as equal will misallocate attention. The practical outcome is that prioritisation has to become a repeatable governance process, not an ad hoc analyst judgement.
A question worth separating out:
Q: Who should own threat-informed vulnerability prioritisation in a security programme?
A: Ownership should sit with vulnerability and exposure management, but it must be informed by threat intelligence, operations and business owners. The governance question is not who scans, but who decides what gets fixed first and why. Without clear accountability, prioritisation becomes inconsistent, politically driven and hard to defend to leadership.
👉 Read our full editorial: Threat-informed vulnerability prioritization must outpace AI discovery