CVE-2026-114938, also called Java4Shell, is a vulnerability in the Compiler component of Oracle Java SE, Oracle GraalVM and OpenJDK. A successful attack takes over the Java runtime. It was published on November 17, 2026, and Opensolr was patched against it on November 19, 2026.
01 · At a glance
02 · What it is
The flaw is in the Compiler component of the Java runtime. Oracle rates it as difficult to exploit, but it needs no account and no user action: an attacker with network access can trigger it by supplying data to the affected APIs, for example through a web service that runs on Java.
A successful attack results in the takeover of the Java runtime: the attacker reads and changes what the application can read and change, and can stop it.
03 · Who is affected
- Any service that runs on an affected Java version and accepts input from a network: application servers, search engines, message brokers, build servers.
- The version that matters is the one the running process uses, not the newest one installed on the machine.
04 · How to fix it
Install the fixed release of your Java distribution, then restart every Java process. A running JVM keeps the old code in memory until it is restarted.
java -version sudo apt update && sudo apt install --only-upgrade 'openjdk-*' sudo systemctl restart your-java-service
The fixed build has a different name in each distribution (Oracle, Eclipse Temurin, Amazon Corretto, Azul, Red Hat, Ubuntu). Follow the advisory of the one you run.
05 · How to mitigate until you can upgrade
- Expose Java services only to the clients that need them: firewall rules, private networks, a reverse proxy with authentication in front.
- Move services that can run on Java 11 or on a standard Java 8 build to one of those, which are outside the affected range.
- Plan the restart together with the upgrade. An upgraded package with an old process still running is not a fix.
06 · How to check a server
java -version for p in $(pgrep java); do echo "$p $(readlink /proc/$p/exe) started $(ps -o lstart= -p $p)"; done
A path that ends in (deleted) means the process still runs a Java binary that has since been replaced on disk and needs a restart.
07 · Opensolr and this vulnerability
Status on November 20, 2026. Opensolr is patched against CVE-2026-114938. The fixed Java release was installed on November 19, 2026. Nothing is required from you: your Opensolr Index, your account and your data are not exposed to it, and you can keep indexing and querying as usual.
- Opensolr watches newly published vulnerabilities for every component of the platform, around the clock.
- Each advisory is assessed against the platform as soon as it is published.
- The fix is applied, or the vulnerable condition is closed, and the result is verified before the case is closed.
More on how Opensolr protects your data: Opensolr Trust Center and all security pages. Questions about a vulnerability that is not listed: contact Opensolr.
Official sources: Oracle security alert, November 2026 · CISA alert · NVD entry.