Java4Shell (CVE-2026-114938): Omniscope is not affected

Omniscope is not affected by Java4Shell (CVE-2026-114938), the OpenJDK vulnerability disclosed on 17 November 2026. Omniscope 2026.2, the latest version at the time of writing, and all earlier versions ship with Java 11, which doesn't contain the code the flaw lives in. For the Java that comes with Omniscope, you don't need to patch, restart or change any settings.

We checked the OpenJDK 11 source and the Java runtime in each Omniscope installer (Windows, macOS and Linux). The table below shows what we found, so you can pass it to your security team.

CVE-2026-114938 is a flaw in a processor-specific decoder that newer Java switches on

CVE-2026-114938, nicknamed Java4Shell by the researchers who reported it, is listed in the OpenJDK Vulnerability Advisory of 17 November 2026 and in Oracle's November 2026 Critical Security Patch Update. The advisory rates it 8.1 out of 10 and puts it in HotSpot's compiler component.

It is a memory-corruption bug in an optimised version of Java's Base64 decoder, which newer OpenJDK releases switch on automatically on Intel and AMD processors with AVX-512 support. A specially crafted string can make it write outside its memory, which an attacker may use to read data or run code. Any Java application that passes Base64 text from outside to that decoder, in a login header or a file upload for example, can reach it. The researchers' technical write-up has the detail.

The advisory's risk matrix marks the CVE as affecting Java 17, 21, 25 and 27. Java 8 and 11 aren't marked.

Java 11 has no accelerated Base64 decoder, so the flawed code isn't there

Java 11 can decode Base64, but only with plain Java code. The processor-specific speed-up in Java 11 exists for encoding, and none was ever written for decoding. We checked this two ways, after confirming which Java each installer contains:

What we checked What we found
The Java runtime inside each installer (Windows, macOS, Linux) Eclipse Temurin 11, the same version on all three
The OpenJDK 11 source for that exact version Accelerated Base64 code for encoding only. None for decoding
The compiled Java virtual machine in each installer (libjvm.so, jvm.dll, libjvm.dylib), listing the routines built into each file Encoding routine present. No decoding routine

The source and the shipped binaries agree: both have the encoding routine and neither has a decoding routine. The result doesn't depend on the processor.

What you need to do

Nothing. There is no Omniscope update for this, and you don't need the Java options (-XX:-UseBASE64Intrinsics or -XX:UseAVX=2) that scanners and advisories suggest for Java 17 and later.

This applies to the Java that comes with Omniscope, which Omniscope should always run on. We assume you haven't replaced it with a Java of your own.

If your scanner flags Java4Shell on an Omniscope server, send the finding and your Omniscope version to our support team and we'll look at it with you.

Last checked 18 November 2026.

Last updated on 18 November 2026

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article