Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Catch up on the newest Qlik features and improvements: Learn More
cancel
Showing results for 
Search instead for 
Did you mean: 
quentin-vigne
Partner - Creator II
Partner - Creator II

Java4Shell (CVE‑2026‑114938) — Impact on Talend Remote Engine and Talend Runtime

Hi Qlik Talend team,

We’re assessing the impact of Java4Shell (CVE‑2026‑114938) on our Talend Batch and ESB environments. The Remote Engine and Talend Runtime instances we checked both use Azul Zulu OpenJDK 17.0.18+8-LTS.

  • Talend Remote Engine (Batch) — The running JVM reports UseBASE64Intrinsics = false and UseAVX = 2.
  • Talend Runtime 8.0.1-R2025-02-RT (ESB) — The running JVM reports UseBASE64Intrinsics = true and UseAVX = 3, but AVX‑512 VBMI is absent from the CPU features visible to the JVM.

Based on these checks, the affected decoding path appears unavailable in both JVMs. We’d like to confirm Qlik’s assessment and the supported remediation.

  1. Which versions of Talend Remote Engine and Talend Runtime does Qlik consider affected? Is there an official advisory available or planned?
  2. Can we upgrade the JDK in place to a fixed Azul Zulu Java 17 build, such as 17.0.21.1+2, with our existing Talend versions? Is a Talend patch or upgrade also required?

Thanks in advance for any guidance or links to official documentation.

Labels (3)
0 Replies