69% of Security Leaders Say AI Attackers Outpace Their Patching
Azul's survey of 300 security leaders finds 85% hit by patching-related incidents; testing adds 4+ days at 58% of Java-heavy organizations.
By Nathan Brooks
4 min read

What's News
- 69% of surveyed security leaders say AI-equipped attackers can build an exploit within three days; 44% of their organizations need four days or more to patch.
- 85% reported an incident, suspected incident, or near miss attributable to slow patching.
- Testing Java runtime updates adds four or more days to the patch cycle at 58% of organizations.
- Only 19% say at least 90% of their production Java runtimes run the latest security patch.
- Fieldwork ran August 3–7, 2026 among 300 U.S. security leaders at firms with 1,000+ employees.
Sixty-nine percent of U.S. security leaders believe AI-equipped attackers can build a working exploit in three days or less, yet 44% of their organizations need four days or longer to patch a critical vulnerability across production. That mismatch sits at the center of Azul's 2026 AI Vulnerability Gap Report, based on a survey of 300 security leaders commissioned by Azul and conducted by Censuswide.
The headline number is blunt: 85% of respondents reported an incident, suspected incident, or near miss attributable to slow patching. Read that carefully. It's self-reported experience, not a verified breach rate, and it doesn't prove AI caused those events.
Still, the underlying split tells practitioners something uncomfortable. At the one-day threshold, 22% expect attackers to move within 24 hours, while only 13% say their own organization can deploy a fix that fast. Overall, 56% claim production-wide patching in three days — 13% in under 24 hours, 43% in one to three days. The rest need four to six days (32%) or longer (12%).
Azul co-founder and CEO Scott Sellers put it plainly: "Our research shows security leaders understand the threat: awareness is no longer the gap; execution is."
What's actually slowing patches down?
Testing, mostly. At 58% of surveyed organizations, testing Java runtime updates adds four or more days to the patch cycle — 36% report four to six days and 22% a week or longer. Nobody said they skip testing, and there's a good reason: runtime changes touch many applications, and a security update that breaks a critical service creates a new operational problem.
The reported barriers stack up like this:
- 44% cite extensive testing requirements
- 40% point to the complexity or age of affected systems
- 36% flag limited visibility into known vulnerabilities
- 25% blame vendor patch delays
The pattern puts most of the remediation challenge inside the enterprise's own deployment process, not the vendor's release queue.
How bad are the incidents and inventory gaps?
Fifty-five percent report a confirmed incident attributable to slow patching; 53% report a near miss. Those overlap — respondents could pick multiple answers — and the 85% headline figure also includes suspected incidents. The survey doesn't establish that all events involved Java vulnerabilities, though participants come from Java-heavy organizations.
Inventory is the quieter problem. Only 19% say at least 90% of their production Java runtime estate runs the latest security patch level. About one in five admit half or less of their estate is current. And 51% acknowledge partial or limited visibility into critical Java runtimes, including embedded, legacy, and unmanaged instances. A patch can't close exposure on a system the deployment process never reaches — finding a vulnerable runtime inside a packaged application or container is harder than tracking a centrally managed install.
Azul separately assessed 26 quarterly OpenJDK updates spanning more than six years and classified six — 23% — as causing a serious regression. That's the vendor's own release assessment, not a survey estimate of how often a customer's application breaks. The report argues update scope adds to the burden because full OpenJDK quarterly releases bundle non-security changes alongside vulnerability fixes.
What does this change for security teams?
Azul's answer is partly commercial. Its security-update offering limits selected releases to security fixes on a previously stabilized OpenJDK baseline, with quarterly, targeted monthly, and out-of-cycle updates — reducing the unrelated change teams must validate before deploying an urgent fix. Its Java inventory and vulnerability tooling addresses the other side: mapping runtimes, versions, and exposure so a new disclosure connects to affected systems. Azul sponsors the report and sells products targeting the problems it measures; the research includes no controlled comparison showing how much adopters would improve.
The report's practical takeaway is narrower than its product pitch: track the whole path from disclosure to remediation — which systems are affected, who owns them, what testing is required, and whether the fix actually reached production. A deadline only works when teams can verify completion across the estate.
For the next year, 32% of respondents name faster and more frequent patching as their primary exposure-reduction strategy, 26% favor better software and runtime inventory, and 17% prioritize detection and response instead. The fieldwork ran August 3–7, 2026, among security leaders at organizations with at least 1,000 employees and significant Java/JVM production use — self-reported responses from a defined population, not a census of enterprises.
The clearest implication: patch speed and runtime visibility have to improve together. A rapid fix has limited value if the organization can't identify every affected deployment or confirm the update reached it.
Source: unite.ai
More from Nathan Brooks
Show full bio
News editor covering regulation, policy and their impact on entrepreneurship, startups and venture funding at Business Bearings.
2,230 articles