InformationalVulnerabilityMonitoring

Azul survey claims 85% of Java organisations had patching incident or near miss

Azul’s vendor-commissioned survey of 300 U.S. security leaders claims 85% had a slow-patching incident or near miss; check your Java patch coverage.

Published
Exploitation
No. This is a survey of self-reported incidents and near misses, not a report of exploitation of a specific vulnerability, and it is not independently verified.

What happened

According to Azul, an enterprise Java vendor, it released “The 2026 AI Vulnerability Gap Report” on 12 November 2026. iTWire published it as a guest research article. Azul says the report is a survey of 300 U.S. security leaders, conducted by Censuswide, at organisations where Java is a significant share of the production application estate. The research was commissioned by Azul. Azul says fieldwork ran August 3 to 7, 2026, at organisations with 1,000 or more employees.

Azul claims 85% of organisations have had an incident or near miss attributable to slow patching. It breaks this down as 55% reporting a confirmed incident and 53% a near miss, and says respondents could select both. iTWire

Other figures Azul attributes to the survey:

  • 69% of respondents believe AI-equipped attackers can build a working exploit within three days or less.
  • Only 13% say they can deploy a critical patch across production in under 24 hours. 43% need one to three days, 32% need four to six days, and 12% need longer. By these figures 56% can deploy within three days and 44% need four days or more.
  • 58% add four or more days of pre-deployment testing to Java runtime updates.
  • Only 19% say nearly all (90% or more) of their production Java estate is on the latest security patch level. 21% say half or less is current.
  • 49% claim full visibility into critical Java runtimes, while 51% say their visibility is partial or limited.
  • 66% have no mandated, time-bound commitment for patching non-critical vulnerabilities.

The release also cites third-party material: an October OpenJDK quarterly update that Azul says disclosed a record 53 vulnerabilities, Mandiant’s M-Trends 2026, Verizon’s 2026 Data Breach Investigations Report, and the October compromise of eight eMudhra intermediate certificate authority keys. According to Azul, Java runtimes keep their own trust stores and do not check revocation by default, so each runtime needed its own update. iTWire

What is not confirmed: the full report was not available in the source, so its methodology cannot be checked. The survey is U.S.-only, and the incidents are self-reported by respondents. No named victim, CVE or specific exploited flaw is given. Azul also sells “Security-only, Stability-first” Java updates and promotes them in the same release, so it has a commercial interest in the findings.

Am I affected?

This is not a flaw in a specific product or version, so there is no affected-version list. The survey describes organisations with a large Java or JVM estate. According to Azul, the barriers respondents cite most are internal:

  • extensive pre-deployment testing (44%)
  • complexity or age of affected systems (40%)
  • limited visibility into known vulnerabilities (36%)

The cited eMudhra example concerns runtimes embedded in applications and containers. Whether you are exposed depends on your own inventory and patch timelines, which the source does not describe for any individual organisation.

What to do now

The source gives no vendor or CERT remediation steps. The steps below follow from the gaps the survey describes and are not sourced instructions.

  1. List every Java runtime you run, including embedded, legacy and unmanaged instances, since Azul says many respondents cannot see all of theirs.
  2. Measure how long a critical Java security update takes from release to full production, including testing, and compare it with your own risk tolerance.
  3. Check what share of your production Java estate is on the latest security patch level.
  4. Check whether you have a time-bound patching commitment for non-critical vulnerabilities, not just a best-effort approach.
  5. If you read the full report, remember it is vendor-commissioned and weigh its recommendations accordingly.

Sources