JetBrains published a security advisory on July 27, 2026 for CVE-2026-63077, an untrusted data deserialization vulnerability affecting all on-premises versions of TeamCity. The bug, rated CVSS 9.8, enables unauthenticated remote code execution through the build agent polling protocol—an unusual vector that turns an ordinary architectural feature into an entry point for compromising entire development pipelines. The maximum severity reflects total impact on confidentiality, integrity, and availability, combined with the absence of authentication prerequisites.
- CVE-2026-63077 is a CWE-502 vulnerability with CVSS 9.8 allowing unauthenticated RCE in TeamCity On-Premises via the agent polling protocol
- The attacker gains server process privileges, with access to stored credentials and the ability to compromise CI/CD integrity
- At the time of disclosure on July 27, 2026, JetBrains had not detected active exploitation
- Patched versions are 2026.1.3 and 2025.11.7; a security patch plugin is also available for legacy installations from 2017.1 onward
The Mechanism: When Agent Polling Becomes a Command Tunnel
The vulnerability lies in the handling of the polling protocol TeamCity uses to coordinate build agents. According to Rapid7's analysis, a remote attacker with simple HTTP(S) access to the server can inject malicious serialized objects that, during deserialization, execute arbitrary operating system commands with the privileges of the TeamCity server process. The CVSS:3.1 vector confirms the maximum risk configuration: network access without authentication, low attack complexity, no user interaction required.
"An unauthenticated remote attacker with HTTP(S) access to a TeamCity server can exploit the agent polling protocol to bypass authentication checks and execute arbitrary operating system commands with the privileges of the TeamCity server process." — Rapid7 advisory, CVE-2026-63077
The agent polling protocol is fundamental to TeamCity's distributed architecture: it allows servers to assign build jobs, receive artifacts, and monitor worker instance status. That this operational channel becomes an attack surface reveals a recurring pattern in Java enterprise applications: deserialization of internal data streams is often treated as an implicit trust boundary, only to prove exploitable when input is not adequately validated.
Why CI/CD Servers Are Prized Targets
Compromising a continuous integration server does not stop at the host system. "Attackers who exploit the vulnerability can read stored credentials and compromise CI/CD pipeline integrity," JetBrains stated regarding the documented impact. TeamCity stores secrets for repository access, container registries, deployment environments, and infrastructure management systems; their exfiltration opens the door to lateral movement toward downstream assets.
The attack surface of CI/CD servers remains underestimated in many organizations. Often exposed to internal networks but occasionally accessible from the internet to support distributed teams, these systems combine high privileges with high-frequency automated operations. The ability to inject code into a build pipeline enables supply chain attacks with a multiplier effect: a single compromised artifact can propagate to thousands of deployments.
TeamCity Cloud is explicitly excluded from the vulnerability; the impact falls entirely on on-premises installations, typically in enterprise environments with requirements for direct control over build infrastructure. The architectural choice of on-prem, motivated by compliance or latency, here transforms an operational advantage into total security responsibility.
Immediate Actions
JetBrains has released patched versions 2026.1.3 and 2025.11.7, per converging data from Rapid7 and the NVD record. For organizations unable to upgrade immediately, a security patch plugin is available for TeamCity 2017.1 and later; JetBrains emphasizes that the plugin addresses only CVE-2026-63077 and that upgrading to the fixed version remains the recommended solution.
Rapid7 deployed vulnerability checks in its Exposure Command, InsightVM, and Nexpose products on July 28, 2026: organizations using these tools can identify exposed instances in their attack surface. Scanning should prioritize TeamCity servers accessible via HTTP(S) from untrusted networks, with particular attention to those with polling agents configured on broad network segments.
Verifying exposure of the polling protocol adds a specific element to routine checks: many administrators focus on protecting the administrative web interface, overlooking that the agent channel may offer parallel attack vectors. The brief does not document network configurations or segmentation that effectively isolate this traffic.
The dossier does not specify post-compromise detection measures or indicators of compromise (IoCs) to identify potential abusive access to the polling protocol prior to disclosure.
The Achilles Heel of Deserialization in Java Enterprise
CWE-502, deserialization of untrusted data, appears with worrying frequency in security advisories for mature Java platforms. Despite years of awareness and the introduction of mitigation libraries, the pattern persists because it touches internal communication mechanisms designed in eras preceding modern threat models. TeamCity's polling protocol is an emblematic example: a legitimate architectural feature implemented with data streams that assume ambient trust.
The technical reading suggests the fix implies redefining the trust boundary across all server-agent communication channels, not merely adding superficial input filters. The nature of the fix released by JetBrains is not detailed in the public disclosure; the brief contains no analysis of the patched code nor information on any additional hardening introduced in versions 2026.1.3 and 2025.11.7.
The absence of known active exploitation as of July 27, 2026 does not lessen the urgency: CI/CD servers represent high-value targets for actors interested in software supply chain compromise, and the public release of an advisory with sufficient technical details to understand the vector typically accelerates exploit development.
The Horizon: Between Patching and Trust Redesign
The CVE-2026-63077 episode raises architectural questions that go beyond a single vendor. On-premises CI/CD platforms inherit trust models born from monolithic corporate contexts; the extension to distributed teams, hybrid clouds, and extended supply chains demands redesign of security boundaries, not just patch application. The persistence of deserialization vulnerabilities in top-tier enterprise systems indicates the transition is incomplete.
It remains to be seen whether JetBrains will introduce structural changes to the polling protocol beyond the specific bug fix. The brief does not document a security roadmap or preventive hardening initiatives for future releases. Attention now shifts to adoption timelines for patched versions in enterprise installations, often slowed by dependencies on critical pipelines and extended validation cycles.
Sources
- https://www.rapid7.com/blog/post/etr-cve-2026-63077-critical-unauthenticated-remote-code-execution-in-jetbrains-teamcity
- https://nvd.nist.gov/vuln/detail/CVE-2026-63077
- https://www.rapid7.com/platform/
- https://www.rapid7.com/products/command/exposure-management/
- https://www.rapid7.com/products/command/attack-surface-management-asm/
Information verified against cited sources and current as of publication.