CADChain Blog

Java4Shell Engineering Guide: Jenkins, Artifactory and Keycloak Were Shown Exploitable Before Login. What CAD and PLM Teams Should Patch First and Ask Their Vendors | CADChain | CAD DRM & IP

News
TL;DR: What does Java4Shell mean for engineering teams?

Java4Shell (CVE-2026-114938), disclosed on 17 November 2026, is a memory bug in Java's Base64 decoder that hits Java 17.0.6 and newer on x86-64 CPUs with AVX-512 VBMI. Calif ran code without a login on Jenkins, JFrog Artifactory, Keycloak, Jira and Confluence. Patch identity and internet-facing build tools first, check your CPUs, and ask PLM and PDM vendors which Java they ship.
Developing story. Last updated 18 Nov 2026, 10:49 CET. We'll update this article as Oracle, OpenJDK and software vendors publish more.
Here is what happened with Java4Shell and which Java builds fix it; this guide covers Java4Shell for engineering teams: the build servers, artifact stores, code review, search and login systems that sit around your CAD and PLM data.

What we know so far about Java4Shell

  • The bug: on x86-64 CPUs with AVX-512 VBMI, a short malformed Base64 string makes Java's fast decoder write past its memory buffer. Calif shows memory leaks and remote code execution (RCE) without credentials.
  • Red Hat's four conditions: OpenJDK 17.0.6 or later, a VBMI CPU, a JVM not started with -XX:UseAVX=2 or lower, and an app that decodes attacker-controlled Base64, such as login headers, SAML messages, JWTs or cookies.
  • Scores: Oracle 8.1 (CVSS 3.1), Calif 9.2 (CVSS 4.0), Red Hat a preliminary 9.8.
  • Fixes: Qualys, Tenable and CERT-EU list Oracle's fixed builds as 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1.
  • Attacks: none reported in the wild as of 18 November. Calif is holding back its exploit chains, and VulnCheck offers a working RCE exploit to its paying customers only.

Where does Java sit in an engineering stack?

Java runs far more of the toolchain around design data than the PLM server alone. Here is what Calif showed on each layer:
SystemTypical toolWhat it holdsCalif's result
Identity and SSOKeycloak, PingFederateLogins for PLM, build and supplier portalsRCE before login
Build serverJenkinsSource, build secrets, release buildsRCE before login
Artifact storeJFrog ArtifactoryRelease binaries, firmware, design packagesRCE before login
Tracker and wikiJira, ConfluenceSpecs, change requests, test reportsRCE before login
Code reviewGerritSource and review historyRCE after login
Search indexesElasticsearch, SolrIndexed specs and drawing listsRCE after login
PLM, PDM and CADVendor productsModels, drawings, BOMsNot named by any source
RCE lets the attacker run commands with the service's own rights. On a build server that means the secrets it uses to pull code and push releases; on an artifact store, every file you ship. Identity sits in front of all of it, which is why Qualys puts it first.

Which engineering tools did researchers actually exploit?

  • RCE before login: Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate.
  • RCE after login: Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. Red Hat's Bugzilla relay lists Kafka and Gerrit as pre-login.
  • Client side: a Java program that opens TLS to a malicious server can be taken over.
Calif calls this "initial testing" of default setups, and each app needs its own exploit chain. On 18 November Atlassian's latest bulletin didn't mention the CVE, and we found nothing from Jenkins, JFrog or Keycloak. CERT-EU names Keycloak, some Atlassian products and Artifactory as dependent software.

Are CAD, PLM and PDM tools affected by Java4Shell?

Nobody knows yet. No advisory, researcher or vendor names a CAD, PLM or PDM product. Earlier PLM flaws this year, like the Windchill vulnerability, the October patches for Oracle's PLM suite and the 3DEXPERIENCE launcher flaw, were separate product bugs. Java4Shell lives in the Java runtime, so it reaches any product that ships an affected Java and decodes outside input on a VBMI processor.
Bundled runtimes are the blind spot: Qualys warns that OS updates skip a JDK shipped inside a product, and CISA notes it can be missing from inventories. The Swiss NCSC tells operators to "clarify their exposure with their software suppliers". Ask your vendors:
  1. Do the server, portal, connectors or desktop client ship their own Java, and which version?
  2. Is it 17.0.6 or newer, or on the 21, 25 or 27 lines?
  3. Does any part decode Base64 from outside: login headers, SAML, JWTs, cookies?
  4. Do your hosted servers have AVX-512 VBMI CPUs?
  5. When does a fixed Java ship, and do you support -XX:-UseBASE64Intrinsics until then?
  6. Do desktop clients open TLS connections with a bundled Java?

Which CPUs in your server room and on engineers' desks are affected?

  • Servers: Intel Xeon Ice Lake to Granite Rapids, and AMD EPYC Zen 4 and newer. Upwind reproduced the bug on an AWS c6i instance.
  • Workstations: VulnCheck lists 2019 to 2021 Intel client chips (Ice Lake, Tiger Lake, Rocket Lake) and Ryzen 7000 and 9000. With Calif's client-side TLS attack, a Java desktop tool on such a machine is at risk when it connects to a malicious server.
  • Not affected: ARM64 (AWS Graviton, Ampere), x86 chips without AVX-512 VBMI, and most Intel client chips from 12th gen on.
On Linux, grep -o avx512vbmi /proc/cpuinfo | head -1 prints nothing on an unaffected CPU. Qualys adds that moving a workload to another cloud instance type can land it on an affected one.

In what order should an engineering organisation patch?

Based on Qualys's patch priority, mapped onto an engineering team:
  1. Identity in front of PLM and supplier portals: Keycloak, PingFederate, other SSO.
  2. Internet-facing Jenkins, Artifactory, Jira and Confluence.
  3. Other outside-facing Java services that take logins, tokens or uploads.
  4. Internal services: Gerrit, Elasticsearch, Solr, Kafka, Spinnaker.
  5. Vendor-bundled Java in PLM, PDM and CAD servers, as updates ship.
  6. Workstations with affected Intel chips.
Every source says the fix needs a JVM restart, and container images need rebuilding. Some fixes are still missing: Temurin's news page showed no November release, Red Hat had no errata on 17 November, and Debian stable was still marked vulnerable.

Is there a temporary fix if you can't patch today?

Calif's flag -XX:-UseBASE64Intrinsics switches off the faulty fast path, and Red Hat prefers it. The caveats:
  • Tenable notes it isn't in Oracle's or OpenJDK's advisories, so test it on one JVM first.
  • CERT-EU and VulnCheck add a diagnostic-options prefix; sources differ on whether it's needed.
  • -XX:UseAVX=2 switches off all AVX-512 code, and an ARM JVM won't start with it.
  • Upwind warns that a narrower DisableIntrinsic variant set in JAVA_TOOL_OPTIONS caused a fleet-wide outage.
  • Flags need a restart, and Red Hat says to remove them after patching.

Should PLM portals and build servers come off the internet until patched?

Where you can, yes. The Canadian Centre for Cyber Security suggests isolating internet-facing applications until fixed, and watchTowr suggests firewall limits. Qualys warns that input validation won't stop the very short malicious string, and that a reverse proxy is no reliable shield. Watch for JVM crashes, hs_err_pid files and Java processes opening shells or new outbound connections. The Swiss NCSC: "A security update does not remove an existing compromise."

What we don't know yet

  • Whether any CAD, PLM or PDM product ships an affected Java on VBMI hardware.
  • Fixed builds from Temurin, Azul Zulu, Microsoft, Liberica, SapMachine and Red Hat.
  • Statements from Atlassian, Jenkins, JFrog, Keycloak and Ping Identity.
  • When exploit chains go public, and whether attacks follow. Cisco Talos expects probing.
  • Whether standard Java 8 and 11 are affected; Red Hat says OpenJDK 8 and 11 are not.

Java4Shell timeline

  • 22 Oct 2026: Oracle reserves CVE-2026-114938.
  • 17 Nov, 21:00 UTC: Oracle releases its November patch update.
  • 17 Nov: CVE published; CISA and the Canadian Cyber Centre issue alerts; Corretto ships fixes.
  • 17 Nov, 23:00 UTC: VulnCheck's exploit reaches its paying customers.
  • 18 Nov, 10:11 CET: CERT-EU advisory 2026-021 rates the flaw high; the Swiss NCSC warns too.

What this means for you

  1. List every Java service around your design data, vendor-shipped ones included.
  2. Check CPUs on servers, cloud instances and engineering laptops.
  3. Patch in order and restart each JVM.
  4. Send the six questions to your PLM, PDM and CAD vendors today.
  5. Pull exposed portals behind a VPN until patched.
Suppliers without an IT team can use our small business Java check, and freelance CAD designers the Java4Shell patch plan for freelancers. EU teams preparing for vulnerability reporting can read our Cyber Resilience Act reporting guide.
The GitLab vulnerability, the PHP flaw for engineering teams and the Optimizely hack on manufacturer portals hit the same tools around design data. Our guides to CAD file security and CAD version control security cover the files. CADChain adds DRM to CAD files, so a model copied off a compromised build server stays locked to the people you authorised.

FAQ: Java4Shell and engineering teams

What is Java4Shell?

CVE-2026-114938, a memory bug in Java's Base64 decoder disclosed on 17 November 2026. On x86-64 CPUs with AVX-512 VBMI it lets an attacker leak memory, crash the JVM or run code.

Is Jenkins or Artifactory vulnerable to Java4Shell?

Calif showed RCE before login on default Jenkins and JFrog Artifactory setups. We found no comment from either vendor by 18 November. Update the Java runtime under them and restart.

Are engineering laptops at risk?

VulnCheck lists 2019 to 2021 Intel client chips (Ice Lake, Tiger Lake, Rocket Lake) as affected. A Java desktop tool on such a laptop is at risk if it connects to a malicious TLS server.

Is Windchill, Teamcenter or 3DEXPERIENCE affected by Java4Shell?

No source names any CAD, PLM or PDM product. Ask your vendor whether it bundles Java 17.0.6 or newer, runs on AVX-512 VBMI hardware, and when a fixed runtime ships.

Which Java versions fix Java4Shell?

Oracle's fixed builds are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1; Amazon Corretto shipped 17.0.21.1.2 and 27.0.1.1.4. Temurin and Red Hat had no fixed build in the sources we checked on 18 November.

Is Java4Shell being exploited?

No attacks in the wild were reported as of 18 November 2026, and it is not in CISA's Known Exploited Vulnerabilities catalogue. Cisco Talos expects probing to start.

More on this story