Automated Threat Modeling

Overview of CVE-2026-133092: Git Submodule Argument Injection Leading to RCE in JetBrains TeamCity

A brief summary of CVE-2026-133092, a CWE-88 argument injection flaw in JetBrains TeamCity On Premises where Git submodule URLs could lead to remote code execution, fixed in 2026.2.2 and 2026.1.6. Includes patch information and affected version ranges.

CVE Analysis

8 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-19

Overview of CVE-2026-133092: Git Submodule Argument Injection Leading to RCE in JetBrains TeamCity

Introduction

CI/CD servers sit on top of source code, build secrets, and deployment credentials, so a bug that turns repository content into code execution lands directly in the software supply chain. JetBrains has patched a flaw in TeamCity On Premises where Git submodule URLs, which come from inside the repository being built, could be interpreted by Git as command options and lead to remote code execution by a low-privileged user.

The issue is tracked as CVE-2026-133092, rated High with a CVSS 3.1 score of 8.8 by JetBrains as the assigning CNA, and classified as CWE-88 (argument injection). Fixed builds, TeamCity 2026.2.2 and 2026.1.6, shipped on 3 November 2026, roughly two weeks before the CVE record was published on 19 November 2026. At the time of writing, the sources we reviewed report no confirmed exploitation and no public exploit.

Technical information

Root cause: argument injection, not shell injection

The official weakness is CWE-88: Improper Neutralization of Argument Delimiters in a Command. This class covers command construction that fails to preserve the intended boundary between data arguments and options or switches. The attacker does not break out of a shell or chain a second command. Instead, an attacker-controlled value is passed to a program as an argument, and the program reads it as an option rather than as data.

MITRE draws an explicit line between this and OS command injection: filtering shell metacharacters or preventing a separate command from running does not stop an input value from being interpreted as an unintended option to the original command. In this case, a URL value that looks harmless to a shell-oriented filter can still change how Git behaves.

Where the attacker-controlled input comes from

TeamCity's Git VCS root has a submodule setting that controls whether submodule repositories are checked out. Recursive checkout fetches the entire submodule tree, while nonrecursive checkout fetches only directly referenced submodules. When submodules are enabled ("Checkout" or nonrecursive checkout), TeamCity reads submodule URLs from repository content, specifically the .gitmodules file, and passes them to the Git client.

The two kinds of URL sit on different sides of a trust boundary. A VCS root URL is entered through TeamCity's configuration form, but a submodule URL is supplied by whoever can commit to the repository. TeamCity already restricts some URL types on VCS roots: since 2026.1, file:// URLs in Git VCS roots are blocked by default with the error "The URL must not be a local file URL", unless the following property is set:

teamcity.git.allowFileUrl=true

CVE-2026-133092 shows that submodule URLs, which arrive from inside the repository rather than from the VCS root form, needed their own validation.

Prerequisites from the CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
MetricValueMeaning
Attack vectorAV:NNetwork
Attack complexityAC:LLow
Privileges requiredPR:LLow
User interactionUI:NNone
ScopeS:UUnchanged
Confidentiality / Integrity / AvailabilityH / H / HHigh impact

This is a low-privilege vulnerability, not an unauthenticated one. In practice, being able to influence repository content or VCS settings is enough. JetBrains has not identified the exact TeamCity role or permission set that maps to PR:L. The 8.8 score is the JetBrains CNA assessment shown on NVD. NVD had not published its own score in the retrieved record.

Attack flow

Based on the available disclosure, the exploitation path looks like this:

  1. The attacker holds low privileges that let them influence a repository used by a TeamCity Git VCS root, for example push access, or the ability to influence VCS settings.
  2. The attacker commits a .gitmodules file containing a submodule URL crafted so that Git will read it as an option instead of a URL.
  3. A build configuration with submodule checkout enabled checks out the repository, and TeamCity reads the submodule URLs from .gitmodules.
  4. TeamCity hands the URL to the Git client without guaranteeing it is treated purely as positional data.
  5. Git interprets the value as an option, which the CNA record states could result in remote code execution.

What remains unconfirmed

The public material does not disclose the vulnerable method, the exact Git invocation, the malicious URL syntax, the required TeamCity permissions, the execution identity, or whether execution occurs on the TeamCity server, a build agent, or a particular checkout path. VulDB likewise lists the technical details as unknown. We have not reconstructed a payload and do not recommend treating any guessed Git option as the confirmed vector.

Patch information

JetBrains fixed CVE-2026-133092 in two TeamCity On Premises bug-fix releases, both published on 3 November 2026:

Release lineFixed versionBuild
2026.2.x2026.2.2239308
2026.1.x and earlier2026.1.6223074

JetBrains' Fixed Security Issues bulletin names the bug TW-104359: "Remote code execution was possible via Git submodule URLs". It is rated High, credited to the researcher "c0wking", classified as CWE-88, and resolved in 2026.2.2 and 2026.1.6. The two-week gap between the fixed builds and the CVE record is consistent with JetBrains' usual practice of publishing security bulletins after a release.

How it was fixed

JetBrains has not published a source diff, commit, or technical write-up for TW-104359. The YouTrack issue is not publicly viewable and TeamCity's server code is not open source, so there is no verified code snippet to show. Whatever the implementation, the patch has to make sure Git only ever reads a submodule URL as a URL. Fixes for CWE-88 in Git wrappers usually combine three defenses:

  • rejecting URLs and paths that begin with a dash character, so Git cannot mistake them for options
  • inserting the double-dash end-of-options separator before positional arguments
  • allowing only known URL schemes

This is the general pattern for the bug class. JetBrains has not confirmed which of these 2026.2.2 and 2026.1.6 use. MITRE's general guidance for CWE-88 points the same way: pass independent arguments through language or framework facilities instead of building a single command string, and validate untrusted input with an "accept known good" approach.

CVE-2026-133092 is one of 40 security problems fixed in 2026.2.2. The 2026.1.6 notes list 38, although their bulletin link points to version=2026.1.5, which looks like a documentation slip. Several fixes harden the same VCS and Git area, so the submodule fix is part of a wider cleanup rather than an isolated change:

  • CVE-2026-133081: RCE via Git VCS root URLs (CWE-78, TW-104064)
  • CVE-2026-133076: RCE via local repository URLs in Subversion VCS roots (TW-103727)

The fix cannot be applied on its own. It ships inside the full bug-fix build.

Getting the fix

JetBrains' announcement lists three upgrade paths:

  • the built-in automatic update feature
  • a direct download from jetbrains.com
  • pulling the updated Docker image

Bug-fix releases within one major version share the same data format, so 2026.2.x users can move to 2026.2.2, and 2026.1.x users to 2026.1.6, without a backup and restore cycle. The 2026.2.2 upgrade notes list no behavior change specific to Git submodules, but check builds that use unusual submodule URL formats after upgrading, since tighter URL validation could reject them.

We did not identify a CVE-specific workaround. TeamCity documents the submodule checkout settings, but the sources do not establish that disabling submodule checkout fully prevents this vulnerability, so we would not treat that as a substitute for the update.

Affected systems and versions

Release branchAffected range (CNA record)Fixed version
TeamCity 2026.22026.2 up to but not including 2026.2.22026.2.2
TeamCity 2026.1 and earlierAll versions below 2026.1.62026.1.6

These are separate ranges. You install the fixed build for your line, not both. The CNA record encodes the lower boundary of the second range as 0, which is a version encoding convention rather than a real TeamCity release. Installations older than 2026.1 are also affected, and the only fixed builds named are 2026.1.6 and 2026.2.2.

The affected product is TeamCity On Premises. The relevant configuration is a Git VCS root with submodule checkout enabled ("Checkout" or nonrecursive checkout), combined with a user who can influence the repository content or VCS settings.

Vendor security history

TeamCity has a record of serious vulnerabilities, and JetBrains has a record of shipping fixes for them.

  • CVE-2024-27198 and CVE-2024-27199 (2024): authentication bypass flaws rated 9.8 and 7.3 by CERT-EU, affecting versions before 2023.11.4. Rapid7 contacted JetBrains on 19 February 2024 and sent a detailed report on 20 February. JetBrains released TeamCity 2023.11.4 and a security patch plugin on 4 March 2024. That historical plugin is not a remedy for CVE-2026-133092, which has its own fixed version boundaries.
  • CVE-2023-42793 (2023): CISA's joint advisory documents Russian SVR actors, also tracked as APT29, the Dukes, CozyBear, and NOBELIUM/Midnight Blizzard, exploiting this separate flaw against TeamCity servers at large scale beginning in September 2023, usually gaining high-privilege code execution.

That history shows sustained adversary interest in TeamCity infrastructure, but it does not attribute any activity to CVE-2026-133092. For the current issue, Rapid7 reports a CISA KEV status of False and an EPSS value of N/A, and VulDB reports no available exploit. VulDB also labels the issue CWE-77, while the JetBrains CNA record assigns CWE-88. We follow the CNA classification.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization