Saturday, November 21, 2026
HomePHPJava4Shell (CVE-2026-114938): What It Means for TeamCity

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


Information
Safety

Abstract

On November 17, 2026, CVE-2026-114938, a memory-corruption vulnerability within the hardware-accelerated Base64 decoder of a number of Java runtimes, was publicly disclosed. This vulnerability permits malicious Base64 enter to deprave JVM course of reminiscence, probably inflicting a crash or distant code execution.

The problem will not be a vulnerability in TeamCity itself. Nevertheless, TeamCity’s server and construct brokers run on Java variations which will comprise the weak code. Our safety evaluation has recognized a possible exploitation situation, so we strongly advocate updating to the newest model to mitigate the chance.

Advisable actions:

  • TeamCity On-Premises: Evaluate each server node and construct agent, and apply one of many mitigations described under. The entire repair is to replace the Java runtime utilized by every part. You’ll be able to apply an interim JVM flag if a direct replace will not be doable.
  • TeamCity Cloud: Servers and JetBrains-hosted brokers will not be affected. Nevertheless, it is best to nonetheless overview the Java runtimes utilized by self-hosted construct brokers.

Particulars

The vulnerability is in an optimized Base64 decoder that impacts Java runtimes used on x86-64 processors with AVX-512 Vector Byte Manipulation Directions (VBMI). When an software passes attacker-controlled Base64 enter to the affected decoder, the decoder can write previous the tip of a heap buffer and corrupt course of reminiscence. The affect is determined by how the appliance handles that enter.

Publicity is proscribed to programs that meet each of the next situations:

  • They use Java 17, 21, 25, 27, or Oracle Java 8 Efficiency Pack (model 8u511-perf or earlier), with out the suitable safety repair.
  • They use an x86-64 processor with AVX-512 VBMI.

Since TeamCity is a Java software, the publicity of its server and construct brokers is determined by the underlying Java runtime.

What it is advisable to do

1. Determine affected hosts

A number is affected if each of the next situations are true. Run the related checks on each server node and construct agent, together with inside Docker containers.

  1. The Java model is older than the fastened model listed under. Be aware that TeamCity won’t use the identical Java model because the one in PATH. It’s also possible to test the model within the server or agent startup logs.
java -version
  1. The CPU helps the AVX-512 VBMI set extension:
# Affected if returns "avx512vbmi"
grep -Eom1 'avx512_?vbmi' /proc/cpuinfo
# Affected if returns "AVX512VBMI"
sysctl -n machdep.cpu.leaf7_features | grep -ow AVX512VBMI
  • Home windows (PowerShell 7.4+)
# Affected if returns "True"
[System.Runtime.Intrinsics.X86.Avx512Vbmi]::IsSupported

2. Mitigate

There are two mitigation choices:

  • Choice A (advisable): Replace the Java runtime.
  • Choice B: If a direct replace will not be doable, disable the weak intrinsic as an interim mitigation.

After performing both choice, test the end result as described within the Confirm part under.

Choice A: Replace the Java runtime

Replace every affected runtime to a hard and fast construct – one of many variations under or a more recent one:

Launch line Oracle / OpenJDK Amazon Corretto
17 17.0.21.1 17.0.21.1.2
21 21.0.13.1 21.0.13.1.2
25 25.0.5.1 25.0.5.1.2
27 27.0.1.1 27.0.1.1.4
8 (Oracle Efficiency Pack solely) 8u513-perf Corretto 8 will not be affected

For different distributions, use the fastened construct out of your Java vendor.

  • Server: Observe the directions on the Set up non-bundled model of Java web page of the TeamCity documentation. Be aware that <TeamCity Dwelling>/jre takes priority over JAVA_HOME.
  • Agent: Observe the directions on the Path to Java on Agent Machine documentation web page.
  • TeamCity Docker pictures: The photographs for TeamCity 2026.1.6 and 2026.2.2 have been republished with a patched Java runtime – the TeamCity variations themselves stay unchanged. We advocate updating to those pictures. If upgrading will not be possible, comply with these directions to patch your present pictures.

Restart every part and recreate Docker containers.

Choice B: Disable the weak intrinsic

Each of the next JVM choices stop the weak code from operating. Use solely one among them.

  1. Disable the accelerated Base64 routines. The JVM stops utilizing the hardware-accelerated Base64 code and makes use of common compiled code as an alternative. This impacts the efficiency of Base64-heavy workloads:
 -XX:-UseBASE64Intrinsics
  1. Restrict the JVM to AVX2. On this case, the JVM gained’t generate AVX-512 code in any respect (together with Base64 decoded), which has a broader efficiency affect. On ARM64, it prevents startup until -XX:+IgnoreUnrecognizedVMOptions can be set:
 -XX:UseAVX=2

Neither choice comes from Oracle or the OpenJDK challenge: The researchers who disclosed the difficulty recognized them, and safety distributors (Datadog and VulnCheck) have verified them.

To use the chosen choice (proven under as <choice>):

  • Server: Append it to the TEAMCITY_SERVER_OPTS surroundings variable.
  • Agent began by agent.sh or agent.bat: Append it to each TEAMCITY_AGENT_OPTS (the agent course of) and TEAMCITY_LAUNCHER_OPTS (the launcher course of).
  • Agent operating as a Home windows service: In <agent residence>/launcher/conf/wrapper.conf:
    • Add wrapper.app.parameter.<N>=<choice> earlier than the jetbrains.buildServer.agent.AgentMain line.
    • Add wrapper.java.further.<N>=<choice>.
    • Renumber the traces that comply with every insertion.
  • Docker: Append it to the surroundings variables within the server (TEAMCITY_SERVER_OPTS) or agent (TEAMCITY_AGENT_OPTS) containers.

Restart every part and recreate Docker containers. A operating JVM retains the choices it was began with. Take away the choice as soon as the runtime is up to date.

Confirm

Be certain that every TeamCity part is operating on the up to date JDK model or, when you’re utilizing an interim workaround, has been began with the required JVM choice.

You’ll be able to confirm this within the server or agent startup logs. For instance:

... 
Java: 21.0.13.1, OpenJDK 64-Bit Server VM (21.0.13.1+2-LTS, combined mode, sharing), OpenJDK Runtime Atmosphere (21.0.13.1+2-LTS), Amazon.com Inc.; JVM parameters: ...-XX:-UseBASE64Intrinsics
... 

Ceaselessly requested questions

Is TeamCity affected?

TeamCity might use affected Java runtimes on x86-64 hosts. We strongly advocate updating affected Java runtimes on TeamCity servers and construct brokers, or making use of an applicable mitigation.

Do I must improve TeamCity?

The repair is utilized to the Java runtime, and upgrading TeamCity doesn’t essentially substitute it. We are going to present further mitigation mechanisms with the upcoming TeamCity 2026.2.3 and 2026.1.7.

Are ARM CPUs affected?

The weak code exists solely within the x86-64 JVM. ARM64 hosts, together with Apple silicon and AWS Graviton, will not be affected.

Is each x86-64 CPU affected?

Solely processors with AVX-512 VBMI assist operating particular Java variations are affected. Use the detection script to test whether or not this is applicable to a selected host.

Help

For any questions concerning this problem, please get in contact with the TeamCity Help crew by submitting a ticket. To report a safety problem in TeamCity, please comply with our Coordinated Disclosure Coverage.

References

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments