By : Kenny Johnston, Chief Product Officer, Azul
Java runs the systems enterprises can least afford to lose: core banking, trading, e-commerce, identity and claims. It is used by about 90% of Fortune 500 companies, according to The New York Times, and it is long-lived, widely deployed and rarely scrutinized. That is why Java4Shell, a remote code execution flaw in OpenJDK that security firm Calif says it found with AI in about an hour, should be read as a signal and not a one-off. For most of enterprise history, finding and weaponizing a flaw took scarce expertise and time, and that time was the defender’s margin. It made quarterly patch cycles, deployment windows measured in weeks and “best effort” policies defensible. AI has erased that margin: Mandiant estimated the average time to exploit at negative seven days in 2025, meaning attacks typically begin before a patch exists.
Java has now seen three major security events in 28 days: a record 53 OpenJDK vulnerabilities, the eMudhra certificate authority compromise and now Java4Shell. This is not an isolated incident, it is a clear trend. Three clocks govern every disclosed vulnerability, the attacker’s, the vendor’s and the enterprise’s, and only the first two have accelerated. Azul’s 2026 AI Vulnerability Gap Report, a survey of 300 U.S. security leaders, shows the third clock lagging. 69% believe an AI-equipped attacker can build a working exploit in three days or less, yet only 13% can deploy a critical patch in under 24 hours. 58% say testing alone adds four or more days to every Java runtime update, 51% concede they cannot fully see their Java estate, and 85% have already had an incident or near miss because of slow patching. Awareness is no longer the gap. Execution is, and patch velocity has become a first-order business risk. Azul closes that gap for its customers with Security-only, Stability-first™ updates, which contain only security fixes, with no new features or unrelated changes, and are built on the prior quarter’s tested update so they can go straight to production. Azul shipped the Java4Shell fix for Azul Core and Azul Prime customers within an hour of the coordinated release on Nov. 17. It delivered updates for the eMudhra compromise within 24 hours of public disclosure and for all 53 vulnerabilities in October’s record OpenJDK update. Java4Shell is not a zero-day, and as of Nov. 17 no exploitation in the wild had been reported. But the next disclosure will not wait for anyone’s testing cycle.
