Payments are experiencing issues due to temporary restrictions in Russia. If your payment does not go through, please submit a support request.Our support team is available 24/7 — we are always here to help with hosting and server issues.We are now accepting requests for dedicated server rental and colocation services in our data center.Reminder: we recommend enabling backups for additional data protection.A new VPS/VDS lineup with NVMe storage and improved performance is now available.Maintenance work on some servers has been completed. All services are operating normally.
Article4 min readViews3

Java4Shell: What to Check on the Server After Fixing the Java Vulnerability

Oracle released patches for CVE-2026-114938, while Calif researchers demonstrated code execution. We analyze risk conditions, Java versions, and safe update procedures.

Comments 0

Processor under a magnifying glass on a metal stand against a light background
In this article

On November 17, 2026, Oracle released patches for CVE-2026-114938, and Calif researchers published an analysis of Java4Shell—a vulnerability in accelerated Base64 decoding within OpenJDK. Under specific conditions, it allows memory corruption and code execution prior to authentication. Owners of Java applications on VPS and servers should urgently identify the running JVM, hardware conditions, and whether their provider offers the fix.

Who Needs to Check the Application

This concerns the Java runtime environment, not a JavaScript browser error. Base64 encodes binary data as text; its decoding is used, for example, in authentication protocols and uploaded file processing. The flaw lies in a low-level decoder optimization: malformed input can corrupt memory before Java rejects it as invalid.

According to the Calif analysis, the vulnerable path exists in unpatched OpenJDK builds starting from version 17.0.6 and requires an x86-64 processor with AVX-512 VBMI support. The ARM64 architecture is not susceptible to this path. To assess a specific service, it is also crucial to determine whether external input can reach the vulnerable optimization. The mere presence of Java or the processor family name does not prove that such a path is accessible in a running virtual machine.

Calif reported demonstrating code execution before authentication in its tests of Jira, Confluence, Jenkins, and Keycloak. These are findings by researchers, not proof that all installations of these products have been compromised. The news is particularly relevant for those hosting such systems, Java services, or dependent integrations on their own servers. A standard PHP site without such a dependency should not automatically be considered affected.

Versions to check

In the final Oracle matrix for this CVE, the following are listed: Java SE 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, and 27.0.1.0.3; GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3; and GraalVM Enterprise Edition 21.3.20.0.3. This list cannot be replaced with a general list of all versions affected by the November Oracle package. In particular, standard Java 8 and Java 11 cannot be declared vulnerable specifically to Java4Shell just because updates were also released for them.

The official release notes for Oracle JDK dated November 17 list the following new builds:

  • Java 17 — 17.0.21.1+4.

  • Java 21 — 21.0.13.1+4.

  • Java 25 — 25.0.5.1+4.

  • Java 27 — 27.0.1.1+4.

These are Oracle JDK version numbers, not universal identifiers for Temurin, Corretto, Zulu, distribution packages, or GraalVM. You must check with your provider for the security advisory regarding this CVE and the available package, including any backport. There is no need to switch to a different Java branch or change providers blindly just to match a version number.

Safe course of action

  • Find the JVM that actually runs the application: bundled with the product, in a container, or as a separate installation. Verify the version, vendor, and available CPU features for the guest system, then assess external entry points with the application administrator.
  • Before maintenance, save the configuration and necessary data, prepare a recovery plan, and define an acceptable downtime window. Select a patched build supported by your product vendor.
  • Update the runtime or base image and perform the vendor-specified application restart. Verify the running process build: installing a new package does not replace the JVM that continues to execute.
  • Check standard login, file uploads, and critical integrations. If Kerberos is used across domains, test this scenario separately: November Oracle releases also include a new check for cross-domain ticket routing.

Researchers described a temporary disablement of the vulnerable optimization. This is not a universal command: parameters depend on the platform, may affect performance, and can even prevent startup on incompatible architectures. Such an option must be validated by an administrator; it does not replace a patch installation plan. Do not disable authentication or security checks to pass a test.

The researchers' demonstration confirms the possibility of exploitation under the conditions they verified. In the original sources consulted for this material, no confirmation of attacks on real client servers was found. We did not test the General iT infrastructure or our clients' systems and make no conclusions regarding their security.

Information verified on November 18, 2026, at 03:08 MSK. Check with the vendor for the availability of specific packages and updates for the built-in JVM.

Discussion 0

Share your experience and ask questions. Comments without links appear after editorial review.

No comments yet. Start the discussion.