Find out if your Java estate is already exposed, before agentic AI does.

The patch gap used to be a delay. Now it’s an opening.

Quarterly Java Patch Set Update (PSU) releases, internal testing cycles, and regression risk leave most enterprises exposed for days to weeks after the patch vulnerabilities have been disclosed. Agentic AI closes that gap from the other side — exploits are now built and launched in under 5 days against a median 43-day enterprise patch cycle.1

The organization may not know which JVMs remain unpatched from quarter to quarter. Estate sprawl, forked internal builds, and JDKs left behind by old deployments all make manual inventory unreliable.

One command. A full picture of this host’s exposure.

Azul’s Java Estate X-Ray scans the machine it’s run on for every JDK install it can find — standard install paths first, then a full-disk pass if nothing turns up — and checks each one against the current patch-level table, updated with every quarterly and targeted monthly (Critical Security Patch Update or CSPU) release.

What it checks:

• Every standard JDK install location (package managers, SDKMAN, jenv, Gradle-managed JDKs, and more)
• Version and vendor, read directly from the install, not inferred from a path name
• Current patch level against the latest quarterly Critical Patch Update (CPU) and monthly releases
• Unidentified or partial installs that could be remnants of a removed build

What it returns: a clear status for this host — up to date, outdated, undetermined, or no Java found — plus next steps.

Works on: macOS, Linux, and Windows.