Introduction
A path traversal flaw in the way JetBrains TeamCity handled Maven repository settings allowed an authenticated, low-privileged user to achieve remote code execution on the TeamCity server. A CI server typically holds source code, build credentials, and signing material, so code execution on TeamCity is a software supply chain concern, and its impact is not limited to one host.
TeamCity is the continuous integration and delivery server from JetBrains, a company that says it has built tools for software developers since 2000. JetBrains states that TeamCity is trusted by more than 30,000 DevOps teams, a vendor-supplied figure rather than an independent market share measurement. In 2023, CISA documented Russian SVR exploitation of a different TeamCity flaw (CVE 2023 42793) and described potential access to developer source code and signing certificates.
Technical information
What has been disclosed
The official description is short. In JetBrains TeamCity before 2026.2.2 and 2026.1.6, remote code execution was possible via Maven repository settings. JetBrains, acting as the CNA, scored it CVSS 3.1 8.8 (High) with the following vector:
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
In plain terms:
- AV:N: reachable over the network
- AC:L: low attack complexity
- PR:L: requires only a low-privileged, authenticated account
- UI:N: no user interaction required
- S:U: scope unchanged
- C:H / I:H / A:H: high impact to confidentiality, integrity, and availability
JetBrains tracks the issue internally as TW 104016 and credits Antoni Tremblay as the reporter.
Root cause class: CWE 23, Relative Path Traversal
The CVE record assigns CWE 23 (Relative Path Traversal). MITRE defines this weakness as externally influenced input used to construct a pathname that can resolve outside an intended restricted directory because sequences such as ../ are not properly neutralized.
Applied to this CVE, the CWE tag indicates that a value in TeamCity's Maven repository configuration was treated as a filesystem path without adequate validation, so relative traversal sequences could point outside the intended directory. JetBrains has not published code-level details, so this is an inference from the CWE classification, not confirmed vulnerable code.
Where Maven settings live in TeamCity
TeamCity documentation describes two ways Maven settings reach the server:
- The TeamCity server itself invokes Maven for server-side functions, including Maven dependency triggers and Maven model display.
- Maven settings files can be uploaded in project settings and are stored in project configuration data.
So the server process consumes Maven configuration, not only the build agents. The documentation does not, however, identify the exact field or code path involved in CVE 2026 133080.
Likely attack flow (inferred)
Combining the CVSS vector, the CWE class, and the documented Maven integration, the attack plausibly follows this shape. Each step beyond the first is inference, not vendor-confirmed detail.
- The attacker holds an authenticated TeamCity account with low privileges (PR:L).
- Over the network, the attacker supplies or modifies a Maven repository settings value that contains relative traversal sequences such as
../. - TeamCity treats that value as a filesystem path without sufficient canonicalization or containment checks, so it resolves to a location outside the intended directory.
- Because the server invokes Maven for its own functions, writing to or pointing Maven at an attacker-chosen location can lead to code execution in the context of the TeamCity server.
What remains undisclosed: the specific vulnerable code, the exact input field, which TeamCity permission is sufficient, and a reproducible exploit sequence. The sources we reviewed reported no public proof of concept or technical exploit details.
Exploitation status
Rapid7 reports that this CVE was not in the CISA Known Exploited Vulnerabilities catalog at the time of its record, and VulDB reports no public exploit or technical details. These are bounded observations about the sources checked, not proof that exploitation has never occurred. No threat actor has been publicly linked to this CVE.
Patch information
JetBrains fixed this issue in TeamCity On Premises 2026.2.2 (build 239308) and 2026.1.6 (build 223074), both released on 3 November 2026. TeamCity is closed source, so there is no public commit, pull request, or diff to inspect. The fix is available only in the vendor's binary releases (official installers, archives, and updated Docker images).
The JetBrains Fixed Security Issues bulletin lists the entry as Remote code execution was possible via Maven repository settings, with internal tracker TW 104016, severity High, weakness CWE 23, fixed in 2026.2.2 and 2026.1.6.
The 2026.2.2 release notes do not list TW 104016 among public issues. They state only that 40 security problems were fixed and point readers to the security bulletin, which JetBrains usually publishes a few days after the release. The 2026.1.6 release notes report 38 security problems fixed.
What the fix likely does
Since no code is public, the following describes the standard remediation for CWE 23 rather than confirmed JetBrains changes:
- canonicalize the user-supplied path (resolving
.., symlinks, and similar constructs), - verify that the resulting path stays inside an allowed base directory, and
- reject or neutralize anything that escapes it.
Part of a wider Maven hardening effort
The same 2026.2.2 / 2026.1.6 release also fixes a closely related issue, CVE 2026 133079 (TW 104014, CWE 829), which allowed RCE through Maven dependencies of Kotlin DSL settings.
Earlier releases had already addressed other Maven-related flaws:
- CVE 2026 132240: XXE through Maven settings file upload (fixed in 2026.1.3 / 2025.11.7)
- CVE 2026 132939: stored XSS in the Maven settings health report (fixed in 2026.2 / 2026.1.4 / 2025.11.8)
CVE 2026 133080 is a separate path traversal bug in this area, so earlier Maven fixes do not cover it. Only builds 239308 or 223074 and later include the fix.
How the fix is delivered
The JetBrains release announcement lists three update paths:
- TeamCity's built-in automatic update
- Downloading the release from jetbrains.com
- Pulling the updated Docker image
Bugfix releases within the same major version share a data format, so you can move between 2026.2.x or 2026.1.x builds without a backup and restore cycle. That statement applies within a series and should not be read as a cross-series migration instruction. TeamCity 2026.2.2 also introduces an automatic security patch installation feature (TW 102418) for delivering future security fixes.
Affected systems and versions
According to the CNA data:
- 2026.2 branch: versions from 2026.2 up to, but not including, 2026.2.2 are affected. Fixed in 2026.2.2 (build 239308).
- 2026.1 branch and older: every version below 2026.1.6 is affected. Fixed in 2026.1.6 (build 223074).
- 2025.11 line: no fixed release exists. The latest build on this line, 2025.11.8, shipped on 2 September 2026, before this fix. Instances on 2025.11 or older need to move to 2026.1.6 or 2026.2.2.
The product affected is TeamCity On Premises. Exploitation requires an authenticated account with low privileges and network access to the server.
Vendor security history
TeamCity's earlier security issues give context, though none of them should be conflated with this CVE:
- CVE 2023 42793: CISA documented Russian Foreign Intelligence Service (SVR) exploitation of this TeamCity vulnerability globally, noting the potential for access to source code and signing certificates. This does not establish exploitation or attribution for CVE 2026 133080.
- CVE 2026 44413: JetBrains published a dedicated blog post describing a high-severity issue affecting TeamCity On Premises and urging an update to 2026.1.
- CVE 2026 63077: JetBrains published additional guidance following reports of active exploitation.
- Maven feature fixes in 2026: CVE 2026 132240 (XXE), CVE 2026 132939 (stored XSS), and CVE 2026 133079 (RCE via Kotlin DSL Maven dependencies), alongside CVE 2026 133080, show JetBrains working through the Maven configuration features one by one.
JetBrains' coordinated disclosure policy states that security fixes are released with a subsequent product release or bugfix update, followed by customer notification and an upgrade recommendation. That matches the pattern seen here.
References
- NVD entry for CVE 2026 133080
- CVE.org record for CVE 2026 133080
- CVE Services JSON record (cveawg.mitre.org)
- JetBrains Fixed Security Issues
- JetBrains Fixed Security Issues, filtered for TeamCity
- TeamCity 2026.2.2 and 2026.1.6 Updates, The JetBrains Blog
- TeamCity 2026.2.2 Release Notes
- TeamCity 2026.1.6 Release Notes
- TeamCity downloads, other versions
- Maven Server Side Settings, TeamCity Documentation
- Maven, TeamCity Documentation
- Security Notes, TeamCity Documentation
- JetBrains Coordinated Disclosure Policy
- Rapid7 Vulnerability Database entry
- VulDB entry 440116
- MITRE CWE 23: Relative Path Traversal
- CISA advisory AA23 347A: SVR exploiting JetBrains TeamCity CVE globally
- JetBrains Blog: High severity issue affecting TeamCity On Premises (CVE 2026 44413)
- JetBrains Blog: CVE 2026 63077 additional guidance following reports of active exploitation
- JetBrains Corporate Overview 2026
- TeamCity product site



