CVE-2026-100253: In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 sandbox escape leading to code execution was possib

This month

HIGH 8.8UPGRADE

CVE-2026-100253 is a high-severity flaw (CVSS 8.8) affecting teamcity. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 sandbox escape leading to code execution was possible via the versioned settings Kotlin DSL

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.4% (top 62%)
CISA exploited list	No
Weakness	CWE-184
Published	2026-09-30
Last modified	2026-10-06

Publisher (CNA): JetBrains s.r.o. · Vendor: jetbrains

Last updated 2026-10-06 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-09-30 16:16 UTCPublished CVE record published
2026-10-06 16:40 UTCUpdated Record last modified

jetbrains teamcity UPGRADE

Affected: < 2025.11.8 · >= 2026.1 and < 2026.1.4

Fixed in: 2025.11.8, 2026.1.4

Safe to downgrade to: a release before 2026.1

1. Check installed version

apt-cache policy teamcity || rpm -q teamcity || teamcity --version

2. UPGRADE to 2025.11.8 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade teamcity

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade teamcity

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2026.1 (Debian / Ubuntu)

apt-cache madison teamcity sudo apt install teamcity=<VERSION_BEFORE_2026.1> sudo apt-mark hold teamcity

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list teamcity sudo dnf downgrade teamcity-<VERSION_BEFORE_2026.1> sudo dnf versionlock add teamcity

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-100253?

teamcity: upgrade to 2025.11.8, 2026.1.4. Exact commands for each OS are on this page.

Is CVE-2026-100253 being exploited?

CVE-2026-100253 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-100253 affect?

CVE-2026-100253 affects teamcity. Severity is high (CVSS 8.8). In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 sandbox escape leading to code execution was possible via the versioned settings Kotlin DSL

How urgent is CVE-2026-100253?

Priority 40/100. High severity

Software pages

JetBrains TeamCity vulnerabilities · Kotlin vulnerabilities

Related CVEs

CVE-2026-44413 HIGH 8.2 UPGRADE In JetBrains TeamCity before 2026.1 2025.11.5 authenticated users could expose server API to unauthorised acce
CVE-2026-59793 HIGH 8.8 UPGRADE In JetBrains TeamCity before 2026.1.2 arbitrary file access was possible via the Perforce VCS integration
CVE-2026-59795 HIGH 8.1 UPGRADE In JetBrains TeamCity before 2026.1.2 stored XSS via unauthenticated agent registration was possible
CVE-2026-59796 HIGH 8.1 UPGRADE In JetBrains TeamCity before 2026.1.2 pipeline modification was possible due to improper permission checks
CVE-2026-59794 HIGH 7.3 UPGRADE In JetBrains TeamCity before 2026.1.2 stored XSS on the cloud profile page was possible via agent-reported dat

References

← Back to latest CVEs