Your ColdFusion hotfixes are current. Your change log shows the update from Adobe's most recent bulletin. Neither fact tells you whether that server is exposed to Java4Shell, because Java4Shell is not a ColdFusion bug. It is a bug in the Java runtime underneath it.
On November 17, 2026, the security firm Calif disclosed Java4Shell (CVE-2026-114938), a memory-corruption flaw in OpenJDK's Base64 decoder that it showed leading to remote code execution. The same day, OpenJDK published its November 17, 2026 vulnerability advisory with fixed releases. The answer for ColdFusion and Lucee servers: find the Java runtime each server actually uses, check it against the advisory, and update that runtime. An Adobe hotfix alone does not do it.
We have built and maintained ColdFusion systems since 1998. On most servers we inherit, nobody can name the Java version without logging in to look.
What is Java4Shell?
Java4Shell is a flaw in the hardware-accelerated Base64 decoding code inside OpenJDK's HotSpot virtual machine. Base64 is how applications carry binary data as text: login tokens, file uploads, API messages. Calif reports that a malformed Base64 string can make the decoder write past the end of its buffer. With enough work, an attacker can turn that into reading server memory or running code. Calif rates it 9.2 out of 10 under CVSS 4.0. Its write-up also notes there is no universal exploit: each application needs its own attack chain.
That last point is not comfort. ColdFusion applications decode Base64 constantly, in authentication, file handling, and integrations, often in code nobody has read in years.
Is my ColdFusion server affected?
A ColdFusion or Lucee server is exposed when two conditions hold, according to Calif's write-up.
The runtime is OpenJDK 17.0.6 or newer, from any distribution. That includes Oracle Java SE, Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, and Red Hat OpenJDK. A server still on Java 11 is outside this particular flaw. The same OpenJDK release still fixes other Java 11 vulnerabilities, so it is not a reason to wait.
The CPU is x86-64 with AVX-512 VBMI support. Calif lists Intel Xeon Ice Lake and later and AMD Zen 4 and later. ARM64 servers are not affected.
Five steps for every ColdFusion and Lucee server
Find the runtime the server actually uses. Do not trust the installed-software list. For Adobe ColdFusion, read the java.home line in the instance's jvm.config. For Lucee on Tomcat, check JAVA_HOME or JRE_HOME in the service configuration. Run java -version with that exact binary.
Compare it to the OpenJDK advisory. The advisory lists the affected versions per Java line. Record the result for each server, not each application.
Update within the same Java major version. Install your distribution's fixed release for the line the server already runs. A jump from one Java major version to another is a ColdFusion migration, not a patch. Confirm with Adobe or Lucee documentation that your engine version supports the target build.
Use the startup flag only as a bridge. Calif documents two mitigations: start the JVM with -XX:-UseBASE64Intrinsics, or with -XX:UseAVX=2. Add the flag to the server's JVM arguments and restart. Use it on x86-64 hosts only. Calif notes that OpenJDK on ARM does not recognize it and fails to start. Remove the flag after the runtime update.
Restart in a planned window and test the login path first. A runtime change touches every application on the instance at once. Test sign-in, file upload, and any integration that exchanges tokens, because those paths decode Base64.
Why the hotfix habit misses this
ColdFusion teams that patch well usually track Adobe's bulletins, as we described in our guide to meeting Adobe's 72-hour patch window. That discipline covers the ColdFusion engine. It does not cover the Java runtime, which ships on its own schedule, usually quarterly, from a separate vendor. We regularly find servers with current hotfixes running a Java runtime that has not changed since the install.
The fix is one line on your patch checklist: Java runtime version, per server, checked every quarter and after every OpenJDK advisory. If you are already planning for ColdFusion 2021's end of support, our first-week list for ColdFusion 2021 is the place to add it.
If you are not sure which Java runtime your ColdFusion servers run, our ColdFusion team can inventory and patch them with you this week.

