Introduction
Continuous integration servers run command-line tools against repositories by design, which turns the boundary between repository data and command arguments into a real security boundary. JetBrains has fixed a TeamCity flaw, CVE-2026-132909, in which the contents of a Mercurial repository could lead to remote code execution. It is rated 8.8 (High) under CVSS 3.1.
JetBrains describes itself as a software company building tools for developers and teams since 2000, and TeamCity is its continuous integration product. The company reports 12.5 million or more recurring active users, more than 4 million customers and 88 customers among the Fortune Global 100 (company-reported figures, not independent market-share data). TeamCity works with several version control systems, including Mercurial, which is the integration at the center of this issue.
Technical information
Key facts
- CNA: JetBrains
- CVSS 3.1: 8.8 High,
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Weakness: CWE-88, improper neutralization of argument delimiters in a command (argument injection)
- Vendor description: "Remote code execution was possible via Mercurial repository contents"
- Internal tracking: TW-102713 (the YouTrack issue is not publicly readable)
- Credited reporter: Antoni Tremblay
- NVD publication: 19 November 2026. NVD displays the JetBrains score but has not published its own assessment.
What is confirmed
The public record is short. JetBrains states that remote code execution was possible via Mercurial repository contents and classifies the weakness as CWE-88. The CVSS vector says the issue is network reachable, has low attack complexity, requires low privileges, needs no user interaction and has high confidentiality, integrity and availability impact with unchanged scope. The record does not name the vulnerable endpoint, repository operation, required TeamCity role or repository configuration. TeamCity is closed source and no source diff or commit is public, so no vulnerable code can be shown.
Likely root cause
Combining CWE-88 with the phrase "repository contents" narrows the bug class considerably. The following is an inference from those two facts. JetBrains has not confirmed it.
- TeamCity uses the standard
hgcommand-line client to work with Mercurial repositories. - Argument injection of this kind occurs when a value taken from the repository, rather than from an administrator-configured field, is placed on the
hgcommand line. Candidate values include a branch, bookmark or tag name, or a subrepository definition. - If such a value begins with a hyphen,
hgparses it as an option instead of as data. - Mercurial options such as its config override option can change client behaviour enough to execute commands.
This moves the trust boundary. The attacker does not need permission to edit the VCS root in TeamCity. They only need to control what goes into a repository that TeamCity checks out, which is consistent with the PR:L rating in the vector.
Inferred attack flow
- The attacker obtains the ability to write content into a Mercurial repository that a TeamCity project is configured to check out.
- The attacker introduces a repository-controlled value (for example a branch, bookmark or tag name, or a subrepository definition) that begins with a hyphen and is crafted to be read as an
hgoption. - TeamCity performs a Mercurial operation against the repository and passes that value to the
hgclient as a command argument. hginterprets the value as an option, such as a configuration override, which changes its behaviour.- The altered behaviour results in command execution in the context in which TeamCity invokes
hg.
This sequence describes the bug class implied by the CWE and description, not a confirmed exploit chain.
How this differs from its sibling CVEs
The same JetBrains bulletin lists other Mercurial issues, and comparing them clarifies what this CVE covers:
- CVE-2026-132234 (TW-101698, Critical): RCE through argument injection in Mercurial VCS root settings, fixed earlier in 2026.1.3 and 2025.11.7.
- CVE-2026-132908 (TW-102712, High): RCE via Mercurial VCS root settings, fixed in the same 2026.2, 2026.1.4 and 2025.11.8 builds as this CVE.
- CVE-2026-132940 (TW-102690, Medium): credential leakage through Mercurial subrepository URLs, fixed only in 2026.2.
The earlier CVE-2026-132234 hardening protected values entered by administrators in VCS root settings. CVE-2026-132909 concerns data arriving from the repository itself, a separate input path, which is why builds that already contained the earlier fix remain vulnerable here.
Patch information
JetBrains fixed CVE-2026-132909 in TeamCity server releases. No public source diff, commit or standalone plugin patch was available for review. All three fixed builds were released on 2 September 2026:
- 2026.2 (major release): build 238924
- 2026.1.4 (2026.1.x branch): build 222865
- 2025.11.8 (2025.11.x and older): build 208382
The release notes do not name the CVE. They report counts only: 130 security problems fixed in 2026.2, 94 in 2026.1.4 and 76 in 2025.11.8. They also state that security bulletins are "typically published few days after the release date." The CVE was added to NVD on 19 November 2026, about 11 weeks after the fixed builds shipped. The NVD affected ranges match these releases.
What the fix most likely does. The code is closed, and JetBrains has not confirmed the technique. The usual remedies for this bug class are:
- Terminating option parsing with the conventional end-of-options marker (two consecutive hyphen characters) before any value that came from the repository.
- Rejecting or escaping values that begin with a hyphen.
- Restricting which configuration overrides or extension settings can reach
hg.
Upgrade guidance. The fix is delivered only inside the server builds above, so remediation means upgrading the TeamCity server to 2026.2, 2026.1.4, 2025.11.8 or a later release in the same branch. To receive every Mercurial fix in this group, including the CVE-2026-132940 subrepository credential leak, upgrade to the 2026.2 line.
Affected systems and versions
Product: JetBrains TeamCity (server).
- TeamCity 2026.1 before 2026.1.4 is affected (NVD range
2026.1 < 2026.1.4). - TeamCity versions before 2025.11.8 are affected (NVD range
0 < 2025.11.8). - The CVE description also states that versions before 2026.2 are affected. 2026.2 is the fixed major release.
- TeamCity 2026.1.3 and 2025.11.7 remain vulnerable, even though they include the earlier CVE-2026-132234 fix for VCS root settings.
The practical exposure condition implied by the description is a TeamCity instance that processes Mercurial repositories. The sources do not specify further configuration requirements or the exact TeamCity privilege needed beyond the PR:L rating.
Vendor security history
TeamCity has a documented history of serious server vulnerabilities. CISA advisory AA23-347a reported that Russia's Foreign Intelligence Service (SVR), also tracked as APT29, exploited CVE-2023-42793 at scale against TeamCity servers beginning in September 2023. JetBrains also published guidance in 2024 on investigating compromised TeamCity servers and on its handling of vulnerabilities disclosed that year.
That history concerns different vulnerabilities. The reviewed sources do not confirm active exploitation of CVE-2026-132909, do not attribute it to any actor and do not link it to CVE-2023-42793. The captured CISA KEV catalog content does not establish whether this CVE is listed, so its exploitation status should be treated as unknown rather than confirmed absent.
JetBrains maintains a coordinated disclosure policy that asks researchers to report through its issue tracker. This CVE was credited to an external reporter and released alongside several related Mercurial fixes, which indicates ongoing hardening of the Mercurial integration across multiple releases.
References
- NVD entry for CVE-2026-132909
- CVE record for CVE-2026-132909
- JetBrains fixed security issues
- JetBrains fixed security issues, TeamCity
- JetBrains fixed security issues, TeamCity 2026.1.4
- TeamCity 2026.2 release notes
- TeamCity 2026.1.4 release notes
- TeamCity 2025.11.8 release notes
- TeamCity 2025.11.8 release notes (2025.11 documentation)
- Tenable Nessus plugin 364474
- VulDB entry for CVE-2026-132909
- CIRT GY advisory ADV2026_642, JetBrains Security Advisory
- Canadian Centre for Cyber Security, JetBrains security advisory AV26 979
- JetBrains Coordinated Disclosure Policy
- CISA Known Exploited Vulnerabilities Catalog
- CISA advisory AA23 347A on SVR exploitation of TeamCity
- JetBrains blog: investigating a compromised TeamCity server
- JetBrains blog: approach to addressing TeamCity vulnerabilities
- JetBrains company page
- JetBrains Corporate Overview 2026
- TeamCity product page



