cimt

Technology

Java4Shell: update Azul Zulu on your Talend machines

Java4Shell (CVE-2026-114938) is a critical flaw in Java 17, 21, 25 and 27. Which Azul Zulu builds fix it, and what to check on your Talend machines.

Wilhelm Oosthuizen ·
#Java4Shell #Talend #Azul Zulu #security #managed services

A serious security flaw has been found in Java: Java4Shell (CVE-2026-114938). Talend runs on Java, so your Talend environment needs action too. The fix is a Java update, available since 17 November 2026.

In short

  • What is it? A flaw in Java 17 (from 17.0.6), 21, 25 and 27. An attacker without an account can use it to run code on a server.
  • What is the impact? Every current Talend installation runs on Java 17 or 21. By 19 November 2026, no successful attack had been confirmed. Security firms do see the first attempts to exploit it, and CISA, the US cyber agency, urges organisations to patch immediately.
  • What should you do? Update Azul Zulu on every Talend machine to the fixed build, then restart the Talend services.

Which Talend machines first

Talend Studio, Talend Remote Engine and Talend Runtime all run on Java 17 or 21. The most urgent machines are those that accept requests from outside: Talend Runtime, data services and REST routes. Remote Engines and Studio follow, because jobs and connections also process data from other systems.

What to do

Update Azul Zulu on every Talend machine to at least the fixed build of the Java line it already runs:

Java lineFixed free Zulu build or later
2727.30.201
2525.38.201
2121.54.201
1717.70.201

Zulu 8 and 11 do not contain this flaw. If they have not been updated since 24 October 2026, though, they miss two critical fixes for compromised certificates (CVE-2026-91403 and CVE-2026-114820), so update them as well.

Our own updates so far taught us three things:

  • Check which Java is the default afterwards. On a server with Java 17 and 21 side by side, the Zulu 17 installer made itself the default Java. Talend can then start on a different Java than before.
  • Look beyond the installed Java. Zulu unpacked from a zip file, a Java bundled inside a Talend folder, and container images need their own update. Remote Engines can also run jobs on a second JDK.
  • Restart the services. A running Talend service keeps the old Java until it restarts. Run one test job per engine afterwards.

If you cannot update straight away, start Java with the option -XX:-UseBASE64Intrinsics. It switches off only the vulnerable part and is a stopgap until the update, not a replacement for it.

How cimt can help

If you would like support with this, our consultants have capacity in the coming weeks to check your Talend environment, plan the update and carry it out with you, including the test runs afterwards.

Updates like this one are part of lifecycle management, a fixed element of our managed services contract. Robin du Maine is happy to explain what that contract offers and how it takes care of updates like this for you. Get in touch through the contact form.

Technical background

For those who want the details: the flaw sits in Java’s fast Base64 decoder. A malformed input makes it write past the end of a buffer before Java rejects the input. The research firm Calif, which found it, showed that an attacker can use it to run code on applications such as Jira, Jenkins and Keycloak. Calif rates it 9.2 out of 10 (CVSS 4.0); Oracle rates it 8.1 (CVSS 3.1).

A server is only exposed when three things come together:

  • an affected Java build;
  • a processor that supports AVX-512 VBMI (Intel Xeon from Ice Lake onwards, AMD from Zen 4 onwards; ARM servers are not affected);
  • untrusted data that reaches Java’s Base64 decoder, for example through a login header or a token.

Sources

Checked on 19 November 2026:

About the author

Wilhelm Oosthuizen

Wilhelm Oosthuizen

Business Engineer

Ask a question →

Frequently asked

About Java4Shell

What is Java4Shell?

Java4Shell (CVE-2026-114938) is a critical flaw in Java 17 (from 17.0.6), 21, 25 and 27. An attacker without an account can use it to run code on a server. Oracle and the OpenJDK project fixed it on 17 November 2026.

Is my Talend environment vulnerable to Java4Shell?

Talend Studio, Talend Remote Engine and Talend Runtime run on Java 17 or 21, both affected Java lines. A server is exposed when it runs an affected Java build, has a processor with AVX-512 VBMI (Intel Xeon from Ice Lake onwards, AMD from Zen 4 onwards) and processes untrusted data. ARM servers are not affected.

Which Azul Zulu build fixes Java4Shell?

The fixed free Zulu builds are 17.70.201, 21.54.201, 25.38.201 and 27.30.201, or later. Update within the Java line the machine already runs.

Do I need to update Zulu 8 and 11 as well?

Zulu 8 and 11 do not contain Java4Shell. If they have not been updated since 24 October 2026, though, they miss two critical fixes for compromised certificates (CVE-2026-91403 and CVE-2026-114820), so update them as well.

What can I do if I cannot update straight away?

Start Java with the option -XX:-UseBASE64Intrinsics. It switches off only the vulnerable part and is a stopgap until the update, not a replacement for it.

Further reading

Ready to apply this?

Book a conversation with cimt and see how these insights fit your data foundation.