TL;DR: Vulnerability volume is rising fast, Flashpoint says, with 21,667 tracked in H1 2026 and one-in-five carrying public exploit code at disclosure. Triage now has to weigh exploitability, exposure, and business impact before severity alone sets the queue.
Editorial analysis by NHI Mgmt Group, based on content published by Flashpoint: “The Flashpoint Method: Prioritizing Vulnerabilities in an Era of AI-Accelerated Discovery”.
By the numbers:
- Some vulnerabilities were weaponized in as little as 24 hours after disclosure, according to Flashpoint.
Key questions
Q: Why isn't CVSS enough for deciding what to fix first?
A: CVSS measures technical severity, but it does not tell you whether exploit code exists, whether the asset is exposed, or whether the weakness sits on a path to sensitive systems.
Q: What happens when exploit code is public before teams finish triage?
A: The remediation queue becomes a race against attacker timing.
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 scoring model Weight active exploitation, public exploit code, asset exposure, business criticality, and remediation effort before assigning queue priority.
- Separate discovery from prioritisation Treat AI-assisted findings as an intake stream, then triage them through explicit criteria so volume does not become the default decision maker.
- Shorten response paths for zero-day-like conditions Escalate vulnerabilities with public exploit code or rapid weaponization into an accelerated review lane with pre-approved remediation options.
Bottom line: AI-assisted discovery increases the number of vulnerabilities teams must evaluate, but it does not reduce the need to judge which ones are exploitable and business-relevant.
Glossary terms: Threat-Informed Vulnerability Prioritization, Exploitability context, Exposure management
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
AI-accelerated discovery creates a prioritisation debt, not just a visibility gain. More findings only help defenders if the organisation can convert volume into ranked action fast enough to matter. Otherwise, AI-assisted discovery floods the queue with unresolved exposure and delays response to the flaws that are already being targeted. The operational issue is not discovery speed alone, but the absence of a decision model that can keep pace with it.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: What should vulnerability teams do when a flaw can affect identity and access systems?
A: Prioritise it higher than an equivalent flaw in a low-impact system because compromise may lead to credential theft, token abuse, or privilege escalation. The right question is not only whether the flaw is severe, but whether it can open a path into authentication, privileged access, or service-account workflows.
👉 Read our full editorial: Threat-informed prioritization beats severity scores for AI-era flaws