Particle.news

JetBrains Tells TeamCity Operators to Patch Java4Shell Flaw in Java Runtimes

A hardware‑accelerated Base64 bug that can corrupt JVM memory to enable remote code execution requires on‑prem TeamCity servers and self‑hosted agents to install fixed Java builds or use verified JVM mitigation flags.

Overview

  • Security researchers disclosed CVE-2026-114938, nicknamed Java4Shell, in mid-November as a memory‑corruption bug in an accelerated Base64 decoder that can crash the JVM or allow attackers to run code.
  • The flaw only affects specific Java release lines (Java 17, 21, 25, 27 and Oracle Java 8 performance builds) when those runtimes run on x86‑64 CPUs that expose AVX‑512 VBMI.
  • JetBrains says TeamCity itself has no code flaw but on‑premises TeamCity servers and self‑hosted build agents are exposed if they run an affected Java runtime without the patch.
  • Vendors published fixed Java builds and JetBrains republished TeamCity Docker images (2026.1.6 and 2026.2.2); operators who cannot update immediately can start JVMs with -XX:-UseBASE64Intrinsics or -XX:UseAVX=2 as an interim mitigation.
  • Full remediation requires replacing running JVM binaries and restarting every Java process, verifying startup logs for the patched version or JVM flags, and hunting for pre‑patch compromise because active scanning was observed after disclosure.