GPU VulnDB

Database/Control plane, storage & DevOps

JetBrains TeamCity: remote code execution via Kubernetes Executor settings

CVSS 7.2CVE-2026-132896Control plane, storage & DevOpscurated

Impact

A user who can change Kubernetes Executor settings can execute code. The record does not say whether the code runs on the TeamCity server or in the Kubernetes cluster that builds are sent to. Either way, a TeamCity server wired into Kubernetes holds cluster credentials, so this can lead from the CI system into the cluster. It needs high privileges, so the main risk is an over-broad admin role or a compromised admin account.

Who can reach it

An authenticated TeamCity user with high privileges, over the network. That means the rights to edit Kubernetes Executor settings, likely an administrator.

What to do

Upgrade the TeamCity server to 2026.2 or later, or 2026.1.4 on the 2026.1 line, and restart it. Builds pause during the restart. Until then, review who can edit Kubernetes Executor settings and keep that list short.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.