SecPod

Learn Search

Search across all Learn content

← Back to Security Research
Critical RCE CVE-2026-132891 Threatens JetBrains TeamCity Through External Pull Requests in November 19, 2026 Disclosure

Critical RCE CVE-2026-132891 Threatens JetBrains TeamCity Through External Pull Requests in November 19, 2026 Disclosure

JetBrains TeamCity faces a broad set of 181 CVE disclosures, led by critical CVE-2026-132891 (CVSS 9.8), an unauthenticated remote code execution flaw involving external pull requests. Explore affected versions, CI/CD security risks, and fixes.

Nov 19, 2026By Aditya Jha9 min read

Critical RCE CVE-2026-132891 Threatens JetBrains TeamCity Through External Pull Requests in November 19, 2026 Disclosure

Summary

JetBrains TeamCity is affected by a Critical remote code execution vulnerability, CVE-2026-132891, associated with the processing of external pull requests. Published on November 19, 2026, the vulnerability carries a CVSS v3.1 score of 9.8 (Critical) and may allow a remote unauthenticated attacker to execute arbitrary code on an affected TeamCity installation.

The vulnerability is classified as CWE-696: Incorrect Behavior Order. According to the published CVE record, remote code execution was possible through external pull requests in affected versions of TeamCity. The CVSS assessment identifies network-based exploitation with low attack complexity, no required privileges, and no user interaction.

TeamCity automates software builds, testing, and deployment through integrations with source code repositories and CI/CD pipelines. External pull requests are a particularly sensitive security boundary because their content may originate from untrusted contributors rather than authorized project maintainers.

Successful exploitation could compromise the affected TeamCity environment. Depending on the execution context and accessible permissions, an attacker could potentially interfere with build processes, access sensitive configuration information, or misuse credentials available to the compromised service.

Disclosure context: CVE-2026-132891 was published as part of a larger collection of 181 TeamCity CVEs covering multiple release branches. This article focuses exclusively on the Critical vulnerability CVE-2026-132891. The remaining 180 CVEs are outside the detailed technical scope of this analysis.

Patch chronology: JetBrains released the relevant fixed TeamCity versions, 2025.11.8, 2026.1.4, and 2026.2, on September 2, 2026. These releases were available 78 days before CVE-2026-132891 was publicly published on November 19, 2026. Organizations should therefore distinguish the original patch availability date from the later public CVE disclosure date.

EPSS and exploitation status: As of November 20, 2026, no EPSS score was available for CVE-2026-132891, and the vulnerability was not listed in CISA's Known Exploited Vulnerabilities (KEV) catalog. The absence of an EPSS score or KEV listing does not establish that exploitation is impossible or has never occurred.

Security updates are available. CVE-2026-132891 is addressed in TeamCity 2025.11.8, 2026.1.4, and 2026.2 within the corresponding release branches. Organizations should upgrade to the latest supported patched release.

Official product information is available through JetBrains' Fixed Security Issues portal and TeamCity Previous Releases documentation.

Vulnerability Details

The following table summarizes CVE-2026-132891, the only Critical vulnerability included in the detailed analysis. The security metadata reflects available public information as of November 20, 2026.

CVE ID CVSS v3.1 EPSS Score CISA KEV CWE Vulnerability Type
CVE-2026-132891 9.8 Critical Not available Not listed CWE-696 Remote Code Execution via External Pull Requests

Security Metadata

Attribute Value
CVE ID CVE-2026-132891
Vendor JetBrains
Affected Product TeamCity On-Premises
Severity Critical
CVSS Version CVSS v3.1
CVSS Base Score 9.8
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE CWE-696: Incorrect Behavior Order
Attack Vector Network
Privileges Required None
User Interaction None
EPSS Score Not available as of November 20, 2026
EPSS Percentile Not available
CISA KEV Status Not listed as of November 20, 2026
Public CVE Disclosure November 19, 2026
Fixed Releases Available September 2, 2026
Patch Availability Yes

Security scoring note: EPSS is a probability-based scoring system maintained by FIRST and is separate from CVSS severity. As of November 20, 2026, an EPSS score had not been published for CVE-2026-132891. No numerical EPSS probability or percentile should be assigned until that information becomes available.

CISA KEV status: CVE-2026-132891 was not listed in CISA's KEV catalog as of the same date. This is a point-in-time status, not evidence that exploitation has never taken place.

Technical Information

Critical - CVSS 9.8 Unauthenticated Network Access CI/CD

CVE-2026-132891 - Unauthenticated Remote Code Execution Through External Pull Requests

CVE-2026-132891 is a Critical remote code execution vulnerability affecting JetBrains TeamCity. The official description states that remote code execution was possible through external pull requests in affected TeamCity versions.

TeamCity integrates with version control systems to monitor repository changes, retrieve source code, process pull requests, and initiate automated builds. External pull requests typically originate from branches or repositories outside the trusted development environment.

These contributions may contain attacker-controlled content. CI/CD platforms must enforce security boundaries when processing external repository information or initiating automated workflows.

The vulnerability is classified as CWE-696: Incorrect Behavior Order. This weakness describes situations in which operations are performed in an unsafe sequence, potentially allowing required validation or security-sensitive operations to occur in the wrong order.

In CVE-2026-132891, the published description associates this weakness with remote code execution through external pull requests. However, the public CVE description does not establish the exact vulnerable functions, complete exploit sequence, or underlying internal execution mechanism.

A successful attacker could potentially obtain code execution within the security context exposed by the vulnerable TeamCity functionality. The resulting access would depend on the affected process, operating-system permissions, and surrounding controls.

CVSS v3.1 Assessment

JetBrains assigns CVE-2026-132891 a CVSS v3.1 base score of 9.8 (Critical).

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Metric Value Interpretation
Attack Vector Network (AV:N) The vulnerability is exploitable over a network.
Attack Complexity Low (AC:L) The CVSS assessment does not require high-complexity attack conditions.
Privileges Required None (PR:N) No authenticated TeamCity account is required.
User Interaction None (UI:N) No separate victim interaction is required.
Scope Unchanged (S:U) The rated impact remains within the vulnerable component's security authority.
Confidentiality High (C:H) Potential significant compromise of sensitive information.
Integrity High (I:H) Potential unauthorized changes to data or operations.
Availability High (A:H) Potential significant service disruption.

Why External Pull Requests Matter

External pull requests are commonly used in collaborative software development. They allow contributors to propose changes without necessarily having direct write access to the target repository.

When a CI/CD system processes these changes, it must distinguish between trusted project configuration and untrusted contribution content.

Improper enforcement of this separation may expose privileged functionality if external inputs influence security-sensitive workflows.

The security implications are particularly important when TeamCity interacts with deployment systems, source code repositories, artifact registries, and other development infrastructure.

The CVE establishes remote code execution through external pull requests, but it does not confirm the use of a specific shell, command interpreter, or post-exploitation sequence.

Patch and Disclosure Timeline

An important characteristic of CVE-2026-132891 is that the relevant corrected TeamCity releases were available before the vulnerability received its public CVE disclosure.

JetBrains' official TeamCity release archive confirms that TeamCity 2025.11.8, 2026.1.4, and 2026.2 were released on September 2, 2026. The CVE record was subsequently published on November 19, 2026.

Date Event Security Significance
September 2, 2026 TeamCity 2025.11.8 released Contains the correction for CVE-2026-132891 in the 2025.11 release branch.
September 2, 2026 TeamCity 2026.1.4 released Contains the correction for CVE-2026-132891 in the 2026.1 release branch.
September 2, 2026 TeamCity 2026.2 released The newer release includes the corrected functionality.
October 5, 2026 TeamCity 2026.1.5 and 2026.2.1 released Subsequent maintenance releases following the initial fixed version boundaries.
November 3, 2026 TeamCity 2026.1.6 and 2026.2.2 released Later maintenance releases available before the public CVE disclosure.
November 19, 2026 CVE-2026-132891 published Public CVE disclosure occurred 78 days after the initial fixed releases.
November 20, 2026 Security metadata reviewed EPSS not available; CVE not listed in CISA KEV.

Disclosure versus patch availability: September 2, 2026 is the relevant fixed-release date, while November 19, 2026 is the public CVE publication date. The later CVE disclosure should not be interpreted as the date when JetBrains first made the corrected software available.

Affected Products

JetBrains TeamCity On-Premises

CVE-2026-132891 affects vulnerable JetBrains TeamCity installations. TeamCity is a continuous integration and build management platform used to automate software development workflows.

The affected functionality involves processing external pull requests associated with version control repositories.

  • TeamCity 2025.11 and earlier affected releases: Versions before 2025.11.8.
  • TeamCity 2026.1 branch: Versions from 2026.1 up to, but not including, 2026.1.4.
  • TeamCity 2026.2: The initial 2026.2 release is identified as a corrected release boundary.

The vulnerability is associated with affected TeamCity software versions rather than a single operating-system platform.

TeamCity Cloud and separately managed services should not automatically be classified as affected without product-specific vendor confirmation.

Affected and Fixed Versions

The applicable corrections for CVE-2026-132891 were released by JetBrains on September 2, 2026, before the vulnerability was publicly disclosed on November 19, 2026.

Release Branch Affected Versions Fixed Version Fix Release Date
TeamCity 2025.11 Before 2025.11.8 2025.11.8 September 2, 2026
TeamCity 2026.1 2026.1 to before 2026.1.4 2026.1.4 September 2, 2026
TeamCity 2026.2 Releases prior to the corrected 2026.2 boundary 2026.2 September 2, 2026

The fixed-version boundaries are 2025.11.8, 2026.1.4, and 2026.2 for the applicable TeamCity release lines.

Organizations running the 2026.2 branch should consider upgrading to 2026.2.2 or a later security-patched release, while organizations using the 2026.1 maintenance branch should consider 2026.1.6 or a later applicable patched release.

These later versions contain additional maintenance and security corrections beyond the initial fix for CVE-2026-132891.

Official release dates and downloads are documented in JetBrains TeamCity Previous Releases Downloads .

Impact

CVE-2026-132891 presents significant security risks because successful remote code execution in CI/CD infrastructure may affect systems responsible for building, testing, and distributing software.

  • Unauthorized Code Execution: A remote unauthenticated attacker may be able to execute arbitrary code through vulnerable external pull-request processing functionality.
  • CI/CD Infrastructure Compromise: Exploitation may compromise the component executing the vulnerable operation, subject to its privileges and isolation controls.
  • Source Code and Configuration Exposure: Repository information, build configurations, or integration data accessible to the affected process may be exposed.
  • Build Pipeline Integrity: If an attacker reaches build configuration or execution functionality, unauthorized modifications could affect generated software artifacts.
  • Credential Exposure: CI/CD environments often contain repository tokens, service accounts, and deployment credentials. Actual exposure depends on the permissions available to the compromised component.
  • Service Availability: Successful exploitation could disrupt TeamCity operations and automated build workflows.

Exploitation status: CVE-2026-132891 is a published Critical remote code execution vulnerability. As of November 20, 2026, it had no available EPSS score and was not listed in CISA's KEV catalog.

These metadata conditions do not independently establish whether exploitation has occurred. No verified post-compromise campaign behavior is asserted here.

MITRE ATT&CK Mapping

The following MITRE ATT&CK mapping is limited to CVE-2026-132891. It distinguishes potentially applicable techniques from activities not established by the public vulnerability record.

T1190: Exploit Public-Facing Application is relevant only in a hypothetical scenario where an attacker exploits an Internet-facing vulnerable TeamCity deployment to obtain initial access. Network reachability alone does not establish this mapping.

Tactic Technique ID Technique Name Context
Reconnaissance N/A N/A No confirmed reconnaissance activity associated with CVE-2026-132891.
Resource Development N/A N/A No confirmed attacker infrastructure or resource preparation.
Initial Access T1190 Exploit Public-Facing Application Hypothetical only. Applicable if an attacker exploits CVE-2026-132891 against an Internet-facing vulnerable TeamCity application to obtain initial access.
Execution N/A N/A The vulnerability permits remote code execution, but the disclosure does not establish abuse of a command or scripting interpreter. T1059 is not assigned.
Persistence N/A N/A No observed persistence mechanism.
Privilege Escalation N/A N/A CVE-2026-132891 establishes RCE, not a separate privilege-escalation mechanism. T1068 is not assigned.
Stealth N/A N/A No confirmed concealment or stealth-related exploitation behavior.
Defense Impairment N/A N/A No confirmed impairment of security controls.
Credential Access N/A N/A Credential exposure is a potential downstream risk, but no specific credential access technique is established.
Discovery N/A N/A No confirmed system or network discovery.
Lateral Movement N/A N/A No established lateral movement activity.
Collection N/A N/A No confirmed information collection technique.
Command and Control N/A N/A No identified command-and-control mechanism.
Exfiltration N/A N/A No confirmed data exfiltration activity.
Impact N/A N/A No specific observed ATT&CK impact technique has been established.

Mapping clarification: Remote code execution does not automatically establish T1059, Command and Scripting Interpreter. Similarly, CVE-2026-132891 does not independently establish T1068, Exploitation for Privilege Escalation.

T1190 is retained only as a possible Initial Access technique for exploitation of an Internet-facing vulnerable TeamCity application. It is not evidence of confirmed exploitation.

Mitigation and Recommendations

Immediate recommendation: Upgrade vulnerable TeamCity installations to a supported release containing the fix for CVE-2026-132891. The corresponding corrected releases are 2025.11.8, 2026.1.4, and 2026.2, all released on September 2, 2026.

The fact that these patches were available before the public CVE disclosure means organizations may already be protected if they have applied the relevant updates. Version verification remains necessary.

Upgrade JetBrains TeamCity

Administrators should identify their installed TeamCity server version and compare it with the affected and fixed release boundaries.

Obtain the relevant updates from the official JetBrains TeamCity Download page.

Before upgrading, back up the TeamCity database, data directory, and relevant configuration files according to JetBrains recommendations.

Verify compatibility with installed plugins and build agents before deploying the updated release.

Restrict External Pull Request Processing

Until vulnerable installations have been patched, review TeamCity configurations that automatically process pull requests from external or untrusted contributors.

  • Restrict automatic execution of untrusted external pull-request builds where feasible.
  • Require review or approval before running untrusted contribution workflows.
  • Use isolated build agents for untrusted repository content.
  • Avoid exposing production deployment credentials or sensitive secrets to external pull-request builds.
  • Review repository trigger rules, branch filters, and access policies associated with external contributors.

These measures are compensating controls, not verified complete workarounds for CVE-2026-132891. Applying the relevant fixed TeamCity release remains necessary.

Protect CI/CD Credentials

TeamCity installations may interact with repository tokens, SSH credentials, deployment secrets, artifact registries, and external automation services.

Organizations should apply least-privilege permissions to these integrations and avoid granting build processes unnecessary access.

  • Use narrowly scoped service accounts and repository tokens.
  • Separate production deployment credentials from untrusted build environments.
  • Restrict TeamCity administrator access to authorized personnel.
  • Review credential usage and rotate secrets when evidence suggests unauthorized access.

Harden Build Agents

Build agents execute automated workloads and may access sensitive development resources. They should run with permissions appropriate to their assigned tasks.

  • Avoid running build agents with unnecessary administrator or root privileges.
  • Use dedicated agents for untrusted builds.
  • Restrict network connectivity to required services.
  • Maintain supported TeamCity plugins and build-agent software.

Monitor Suspicious Activity

Review TeamCity audit records, build histories, repository integrations, and operating-system telemetry for unusual behavior.

  • Unexpected external pull-request build execution.
  • Unrecognized changes to build configurations or repository triggers.
  • Suspicious processes initiated by TeamCity components or build agents.
  • Unauthorized access to repository credentials or deployment secrets.
  • Unexplained changes to build artifacts, publishing destinations, or release workflows.

Verify Remediation

After applying the security update, verify that the TeamCity server reports the expected patched version and that the installation operates normally.

Confirm that build agents reconnect, repository integrations function correctly, and important build pipelines complete successfully.

Reassess the TeamCity installation against CVE-2026-132891 to confirm that the affected version is no longer present.

Administrators should also periodically review updated EPSS information and CISA KEV status. Both are time-sensitive sources and may change after the publication of this article.

For official vulnerability and release details, consult JetBrains' Fixed Security Issues portal and TeamCity Release Archive .

Instantly Fix Risks in Endpoints & Cloud with Saner

Saner is a continuous and integrated vulnerability & exposure management platform that instantly fixes risks in endpoints and cloud.

Featured Posts

Open Adobe Animate CVE-2026-114938: Dependency Patch and Exploitation Analysis - November 19, 2026
Adobe Animate CVE-2026-114938: Dependency Patch and Exploitation Analysis - November 19, 2026

CVE Research

Adobe Animate CVE-2026-114938: Dependency Patch and Exploitation Analysis - November 19, 2026

Adobe APSB26-208 addresses CVE-2026-114938 through an Oracle JDK dependency update in Adobe Animate. This analysis covers affected Windows and macOS versions, the Java4Shell proof of concept, reported probing, technical prerequisites, and verified patch guidance - without assuming an Adobe-specific exploit.

Nov 20, 2026

Open 4EverAble2Shell: From a Security Hotfix to Root Compromise
vulnerability research4EverAble2Shell: From a Security Hotfix to Root Compromise

CVE Research

4EverAble2Shell: From a Security Hotfix to Root Compromise

Nov 20, 2026

Open 10 NGINX Vulnerabilities Disclosed in November 2026: Impact, Exploit Status, and Remediation
10 NGINX Vulnerabilities Disclosed in November 2026: Impact, Exploit Status, and Remediation

CVE Research

10 NGINX Vulnerabilities Disclosed in November 2026: Impact, Exploit Status, and Remediation

Nov 19, 2026

Open ArangoDB Authentication Bypass: CVE-2026-126755 Enables Unauthenticated Superuser Access
ArangoDB Authentication Bypass: CVE-2026-126755 Enables Unauthenticated Superuser Access

CVE Research

ArangoDB Authentication Bypass: CVE-2026-126755 Enables Unauthenticated Superuser Access

CVE-2026-126755 is a critical ArangoDB authentication bypass vulnerability affecting versions before 3.12.11. Learn how inconsistent URL parsing can enable unauthenticated superuser access, its security impact, and recommended detection and remediation measures.

Nov 19, 2026