Particle.news
Download on the App Store

Java4Shell Vulnerability Forces TeamCity Operators to Patch Java Runtimes

Crafted Base64 input can corrupt JVM memory, risking remote code execution on Java runtimes that use AVX‑512 VBMI CPUs.

Overview

  • The bug, which was disclosed on Tuesday, November 17, 2026, is a memory‑corruption flaw in a hardware‑accelerated Base64 decoder that can write past a heap buffer and crash or allow remote code execution in the JVM.
  • A host is exposed only if it runs an unaffected Java build from the Java 17, 21, 25, 27 lines or Oracle Java 8 Performance Pack and uses an x86‑64 CPU that reports AVX‑512 VBMI, so ARM64 machines are not vulnerable.
  • JetBrains published TeamCity guidance on Friday telling on‑premises operators to update to fixed Java builds or, as a stopgap, restart JVMs with -XX:-UseBASE64Intrinsics or -XX:UseAVX=2 and to use republished Docker images for 2026.1.6 and 2026.2.2 that include patched runtimes.
  • Complete remediation requires installing vendor fixed builds (for example OpenJDK/Oracle 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1 or Oracle 8u513‑perf) and restarting services because the mitigations only take effect at JVM startup and the interim flags can reduce Base64‑heavy performance.
  • Teams should hunt for pre‑patch compromises because scanning activity was observed after disclosure and successful exploitation needs heap grooming and address leaks, so defenders and vendors are continuing to monitor for probes and attacks.