Topic starter
19/08/2026 3:52 pm
TL;DR: AI-driven vulnerability discovery is compressing the window between disclosure and exploitation, while CVE volume is rising fast enough to overwhelm manual triage, according to Cycode's analysis of Mythos, Daybreak, and MDASH. The practical implication is clear: security programs now need continuous exposure detection, exploitability context, and machine-speed remediation, not slower patch rituals.
Editorial analysis by NHI Mgmt Group, based on content published by Cycode: “6 Steps to be Mythos Ready: How to Prepare for the AI Vulnerability Storm”.
By the numbers:
- The mean time between public vulnerability disclosure and first observed exploitation has collapsed from 63 days in 2018 to 5 days in 2023, according to Cycode.
Key questions
Q: What should teams do first when AI-driven exploit discovery increases compromise risk?
A: Start with the access paths that would let a single stolen credential turn one foothold into broad internal movement.
Q: Why do some AI CVEs create more operational risk than others?
A: AI CVEs become higher risk when they expose code execution, file access, authentication gaps, or delegated tool access.
Q: What do teams get wrong when they rely on AI to improve vulnerability management too early?
A: Teams often assume AI will reduce risk simply because it increases speed.
Practitioner guidance
- Implement continuous exposure monitoring Track repositories, containers, and deployed services continuously so new CVEs and AI-discovered vulnerabilities are assessed as soon as they appear, not at the next scan cycle.
- Prioritise by exploitability and reachability Use context from code, runtime, and network exposure to decide whether a finding is actually callable, internet-facing, or on a critical path before assigning remediation priority.
- Build a standing vulnerability operations function Assign clear ownership for intake, triage, remediation tracking, and escalation so vulnerability handling operates like a permanent service rather than a project.
Bottom line: AI-assisted vulnerability discovery is collapsing the time available for response, so manual patch rhythms are no longer enough for modern exposure management.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
19/08/2026 4:29 pm
AI vulnerability discovery is now a governance problem, not just a tooling problem. Once models can identify and chain vulnerabilities at scale, the decisive control moves from manual review to continuous exposure management. Security leaders have to govern the intake, ownership, and remediation loop as a standing capability, not an exception process. That means the programme has to understand not only what was found, but what is reachable, exploitable, and still exposed.
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:
A: Start with a discoverable intake path, clear reporting terms, and ownership that routes each finding to the right team without manual confusion. Then test the program under load, because machine-speed discovery will expose weak handoffs, missing embargos, and slow acknowledgements long before a policy review does.
👉 Read our full editorial: AI vulnerability discovery is outpacing patch cycles and governance