CHECKED 17 NOVEMBER 2026

Java build evidence.
Ten JDK CVEs, scoped conclusions.

What the scripts assess

The OpenJDK November 17 advisory lists CVE-2026-114938 through CVE-2026-114947 across Java 8, 11, 17, 21, 25, and 27. The scripts list applicable CVEs for each discovered runtime. Oracle’s Java SE risk matrix has product-specific rows that differ from the OpenJDK source matrix on some lines, so Oracle builds are judged against Oracle’s rows.

The scripts read each runtime’s release file. An exact affected Oracle build is reported as a known affected build. A published Oracle update is reported as updated. Other Oracle builds on a listed line need patch verification. Other OpenJDK distributors and GraalVM need vendor-specific release or backport evidence.

What the result means

A listed version does not prove that an application passes attacker-controlled input to the affected component. A matching update does not prove a running JVM has restarted. A vendor-review result is an inventory finding, not an assertion that the distributor’s build is vulnerable.

By default, Windows scans every ready local fixed drive; Linux and macOS scan from /. The scripts also check PATH, JAVA_HOME, and running process paths. A “no Java found” result means no Java executable was identified within the scan’s time and depth limits. Inaccessible paths, excluded system trees, directory links, archives, containers, and nonlocal drives may still hide runtimes. Check the report’s scope, coverage, and errors before treating an absence as meaningful.

What to do next

For a flagged build, identify the application and the runtime it actually uses. Check whether the affected component handles untrusted input, and ask the software vendor which patched build it supports. If a public-facing service may be exposed and you cannot resolve that quickly, restrict access while you investigate. After updating, restart the application and scan again.

Scope and limitations

The scripts never execute discovered Java binaries, probe an exploit path, update software, or restart services. JavaFX/libxml2 CVE-2026-86144 is a separate issue; runtime release metadata alone cannot establish whether JavaFX is present or loaded. Confirm package provenance and running process state with the owning vendor before closing a finding.

Sources: OpenJDK vulnerability advisory, Oracle November 2026 Critical Security Patch Update. Independent project; not affiliated with Oracle or OpenJDK.

Build a script →