Security Notice: Java vulnerability CVE-2026-114938 (“Java4Shell”)

On 17 November 2026, a critical vulnerability in the Java runtime was made public: CVE-2026-114938, known as “Java4Shell”. It affects Java 17.0.6 and later on x86-64 servers whose processors support AVX-512, which includes most recent Intel Xeon and AMD EPYC servers. An attacker can send crafted input that crashes the server, reads data from its memory, or in some cases runs code remotely, without logging in.

Enonic XP runs on an affected Java version, so installations on affected hardware are exposed.

Enonic Cloud

We have applied a temporary mitigation to all hosted instances. When an updated Java runtime with the permanent fix is available, we will roll it out and let you know.

If you host Enonic XP yourself

Please apply the mitigation now:

  1. Add this option to the JVM options of your Enonic installation:-XX:-UseBASE64Intrinsics[Where to add it, e.g. the environment variable or config file your installation uses for JVM options]
  2. Restart the server. The option only takes effect after a restart.
  3. Check that the running process has the option, for example:ps -ef | grep UseBASE64Intrinsics

The option turns off an optimised Base64 decoder in Java, which is where the flaw is. Java falls back to its standard decoder, so Enonic XP works as before. Workloads that decode large amounts of Base64 may be slightly slower. If you are unsure whether your hardware is affected, apply the option anyway. Remove it once you have installed the permanent fix.

If an internet-facing Enonic XP server has crashed unexpectedly since 17 November, please contact us.

More information

If you have questions, contact us at https://support.enonic.com