Topic starter
28/08/2026 12:04 pm
TL;DR: Only 4.2% of 1,250 plus AI-related CVEs across 50 vendor product types showed evidence of real-world exploitation, even as scanning coverage and CVE volume continue to lag the pace of new disclosures, according to Expel’s SOC analysis. The practical issue is not AI hype, but whether security teams can identify the small set of AI vulnerabilities that actually change risk.
Editorial analysis by NHI Mgmt Group, based on content published by Expel: “The AI CVE exploitation evidence story: Headlines are scarier than reality”.
By the numbers:
- Only 4.2% of the AI-related CVEs Expel tracked showed actual exploitation evidence.
Key questions
Q: What should teams do first when AI CVEs are flooding the queue?
A: Start by separating disclosed AI CVEs into three groups: confirmed exploitation, credible exploit signals, and unproven theoretical issues.
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: How do security teams know if AI is improving vulnerability management?
A: AI is working when it improves decision quality, not just throughput.
Practitioner guidance
- Prioritise AI CVEs by exploit evidence Rank disclosures using exploit activity, vendor advisories, proof-of-concept availability, EPSS movement, and KEV inclusion before assigning remediation priority.
- Validate scanner coverage for AI products Check whether your vulnerability tools publish identifiable coverage for the specific AI platforms, gateways, and agentic tools you operate, not just generic AI support.
- Treat connected credentials as part of AI risk Review tokens, API keys, MCP trust relationships, and delegated access attached to AI tooling so an exploited CVE cannot become an access-control event.
Bottom line: AI CVE disclosure growth is outpacing the number of issues that appear to matter operationally, so exploit evidence is the best first filter.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 19 hours ago by NHI Mgmt Group
28/08/2026 12:04 pm
AI CVE volume is not the same as AI exploitation risk. Expel’s data shows that the market should stop equating disclosure growth with immediate attacker activity. That distinction matters because remediation teams have finite attention, and false urgency can be as damaging as neglect. The practical conclusion is that AI vulnerability governance should prioritise exploitability evidence, not headline count.
A question worth separating out:
Q: What happens when an exploited AI tool can reach connected credentials?
A: The incident stops being a single application flaw and becomes an access-control problem. Once an attacker can use API keys, tokens, or connected services through the AI component, they can move from one vulnerable endpoint into data access, workflow abuse, or broader compromise. That is why identity scope matters in AI triage.
👉 Read our full editorial: AI CVE exploitation is still rare despite rapid vulnerability growth
This post was modified 19 hours ago by NHI Mgmt Group