JetbrainsAndrey KoltsovAnnouncement
Java4Shell (CVE-2026-114938): What It Means for TeamCity
Summary
CVE-2026-114938 is a memory-corruption vulnerability in the hardware-accelerated Base64 decoder of Java runtimes on x86-64 processors with AVX-512 VBMI, affecting Java 17, 21, 25, 27, and Oracle Java 8 Performance Pack. The vulnerability allows malicious Base64 input to corrupt JVM process memory, potentially leading to a crash or remote code execution. TeamCity servers and build agents may use affected Java runtimes, but the vulnerability is not in TeamCity itself. The recommended fix is to update the Java runtime to a fixed build, such as 17.0.21.1 or 21.0.13.1, or to apply an interim JVM flag like -XX:-UseBASE64Intrinsics. TeamCity Cloud servers and JetBrains-hosted agents are not affected, but self-hosted build agents should be reviewed.
Context
CVE-2026-114938 is a memory-corruption vulnerability in the hardware-accelerated Base64 decoder of several Java runtimes (Java 17, 21, 25, 27, and Oracle Java 8 Performance Pack) on x86-64 processors with AVX-512 VBMI. It allows malicious Base64 input to corrupt JVM process memory, potentially causing a crash or remote code execution. TeamCity servers and build agents may use affected Java runtimes, but the vulnerability is not in TeamCity itself.
Approach / What changed
Update the Java runtime to a fixed build (e.g., 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1, or 8u513-perf) or, as an interim mitigation, disable the vulnerable intrinsic by adding the JVM option -XX:-UseBASE64Intrinsics or -XX:UseAVX=2.
Takeaways
The vulnerability affects only x86-64 processors with AVX-512 VBMI; ARM64 hosts such as Apple silicon and AWS Graviton are not affected.
The interim JVM options -XX:-UseBASE64Intrinsics and -XX:UseAVX=2 were identified by researchers and verified by Datadog and VulnCheck, not by Oracle or the OpenJDK project.
TeamCity Docker images for versions 2026.1.6 and 2026.2.2 have been republished with a patched Java runtime; the TeamCity versions themselves remain unchanged.
FAQ
Is TeamCity affected?
TeamCity may use affected Java runtimes on x86-64 hosts. The post strongly recommends updating affected Java runtimes on TeamCity servers and build agents, or applying an appropriate mitigation.
Do I need to upgrade TeamCity?
The fix is applied to the Java runtime, and upgrading TeamCity does not necessarily replace it. The post notes that additional mitigation mechanisms will be provided with upcoming TeamCity 2026.2.3 and 2026.1.7.
Are ARM CPUs affected?
No. The vulnerable code exists only in the x86-64 JVM. ARM64 hosts, including Apple silicon and AWS Graviton, are not affected.
Source and freshness
- Source
- blog.jetbrains.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.