# Java4Shell (CVE-2026-114938): What It Means for TeamCity

DevFeed: [Java4Shell (CVE-2026-114938): What It Means for TeamCity](<https://devfeed.tech/articles/java4shell-cve-2026-114938-what-it-means-for-teamcity-146466.md>)

Original publisher: [Read original article](<https://blog.jetbrains.com/teamcity/2026/11/java4shell-cve-2026-114938-what-it-means-for-teamcity/>)

Author: Andrey Koltsov

Published: 2026-11-20T16:58:43Z

Content type: news

Language: en

Sources: [JetBrains](<https://devfeed.tech/sources/the-jetbrains-blog.md>), [TeamCity](<https://devfeed.tech/sources/teamcity-powerful-ci-cd-for-devops-centric-teams-the-jetbrains-blog.md>)

Topics: [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [teamcity](<https://devfeed.tech/topics/teamcity.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agents](<https://devfeed.tech/tags/agents.md>), [base64](<https://devfeed.tech/tags/base64.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [corruption](<https://devfeed.tech/tags/corruption.md>), [crash](<https://devfeed.tech/tags/crash.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-114938](<https://devfeed.tech/tags/cve-2026-114938.md>), [decoder](<https://devfeed.tech/tags/decoder.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [input](<https://devfeed.tech/tags/input.md>), [it](<https://devfeed.tech/tags/it.md>), [java](<https://devfeed.tech/tags/java.md>), [java4shell](<https://devfeed.tech/tags/java4shell.md>), [jvm](<https://devfeed.tech/tags/jvm.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [memory](<https://devfeed.tech/tags/memory.md>), [memory-corruption](<https://devfeed.tech/tags/memory-corruption.md>), [news](<https://devfeed.tech/tags/news.md>), [november-17](<https://devfeed.tech/tags/november-17.md>), [security](<https://devfeed.tech/tags/security.md>), [teamcity](<https://devfeed.tech/tags/teamcity.md>)

## AI overview

CVE-2026-114938 is a memory-corruption flaw in an optimized Java Base64 decoder, not in TeamCity itself. Risk applies when an unpatched Java 17, 21, 25, or 27 runtime (or Oracle Java 8 Performance Pack 8u511-perf or earlier) runs on x86-64 hardware with AVX-512 VBMI and processes attacker-controlled Base64 input; outcomes may include a crash or remote code execution. Check the runtime actually used and CPU support on every server node and build agent, including containers. The preferred fix is updating each runtime to a vendor-fixed build; TeamCity Docker images 2026.1.6 and 2026.2.2 include patched Java. As an interim measure, use either -XX:-UseBASE64Intrinsics, which affects Base64-heavy workloads, or -XX:UseAVX=2, which has broader performance impact and may prevent ARM64 startup unless IgnoreUnrecognizedVMOptions is enabled. Restart components and verify runtime or JVM options in startup logs. TeamCity Cloud servers and JetBrains-hosted agents are stated to be unaffected; self-hosted agents still need review. ARM64 hosts are unaffected.

## Source excerpt

Summary On November 17, 2026, CVE-2026-114938, a memory-corruption vulnerability in the hardware-accelerated Base64 decoder of several Java runtimes, was publicly disclosed. This vulnerability allows malicious Base64 input to corrupt JVM process memory, potentially causing a crash or remote code execution. The issue is not a vulnerability in TeamCity itself. However, TeamCity's server and build agents [...]