TL;DR: AI-driven vulnerability discovery is compressing defenders' response windows, with Noma Security citing thousands of zero-days found across major operating systems and browsers. Vulnerability programs now need continuous validation and faster prioritisation because backlog exceptions can age out of safe use quickly.
Editorial analysis by NHI Mgmt Group, based on content published by Noma Security: “The Mythos Reality Check: What Does Project Glasswing Mean for CISOs?”.
Key questions
Q: Why do long-accepted vulnerability exceptions become riskier as AI discovery improves?
A: Because the old justification was often that finding and chaining the flaw required rare expertise and high attacker effort.
Q: What are the signs that vulnerability governance is not keeping up with AI-assisted discovery?
A: Look for large exception backlogs, slow triage on high-impact components, long gaps between detection and remediation, and reliance on manual review for assets that change frequently.
A: They should shift from point-in-time vulnerability handling to continuous exposure reduction.
Practitioner guidance
- Re-score legacy exception backlogs Re-evaluate long-standing low-priority vulnerabilities as if advanced exploit discovery is available to adversaries now, not later.
- Shorten vulnerability validation cycles Move from periodic review to continuous validation so triage, testing, and remediation can keep pace with faster discovery.
- Prioritise exploit chains, not single CVEs Identify where individually moderate flaws can combine into privilege escalation or full control paths.
Bottom line: AI-driven discovery compresses the time defenders have to act, so historical exception logic is no longer a safe proxy for risk.
Glossary terms: Continuous validation, Exploit Chain, Exception backlog, Discovery-to-Exploitation Window
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Machine-speed discovery breaks the assumptions behind exception-based vulnerability governance: exception registers were designed for flaws that would remain undiscovered or unexploited long enough for human review cycles to matter. That assumption weakens when models can discover and chain vulnerabilities faster than teams can triage them. The implication is not simply faster patching, but a different governance posture for backlog risk.
A question worth separating out:
Q: How should organisations prioritise continuous validation versus backlog reduction?
A: Use continuous validation to decide which backlog items deserve immediate attention, then reduce the backlog through risk-based sequencing. The priority is not choosing one over the other, but making sure validation keeps feeding the remediation queue fast enough to reflect current exploitability.
👉 Read our full editorial: AI-driven vulnerability discovery is compressing defender response windows