Key Takeaways
- CVE‑2026-63077 (CVSS 9.8) is a deserialization flaw in on‑premise JetBrains TeamCity that permits unauthenticated remote code execution via the agent polling protocol.
- Successful exploitation lets attackers bypass authentication, run arbitrary OS commands with TeamCity process privileges, and potentially access data, configurations, credentials, build artifacts, and downstream CI/CD pipelines.
- CISA has added the vulnerability to its Known Exploited Vulnerabilities (KEV) catalog and mandated patching for Federal Civilian Executive Branch (FCEB) agencies by August 8, 2026 under BOD 26‑04.
- JetBrains has released patches; immediate application is advised for all on‑premise installations.
- The incident underscores the need to secure CI/CD agents, enforce least‑privilege service accounts, and monitor for anomalous polling traffic.
Overview of the Advisory
On August 6, 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) issued an alert regarding a newly patched security flaw affecting on‑premise versions of JetBrains TeamCity. The vulnerability, identified as CVE‑2026-63077, carries a CVSS base score of 9.8, reflecting its critical severity. CISA’s notice highlights that the flaw is already being actively exploited in the wild, prompting urgent remedial action for organizations that rely on TeamCity for continuous integration and continuous delivery (CI/CD).
Vulnerability Description
CVE‑2026-63077 stems from improper deserialization of untrusted data within the TeamCity agent polling protocol. When a TeamCity server listens for polling requests from build agents, it deserializes incoming payloads without adequate validation. An attacker who can reach the server’s polling endpoint—typically exposed on port 8111 or a similar HTTP(S) interface—can craft a malicious serialized object that, when processed, executes arbitrary code in the context of the TeamCity server process.
Technical Mechanics of the Exploit
The exploit leverages Java deserialization gadgets present in the TeamCity classpath. By sending a specially crafted payload through the agent polling request, an unauthenticated remote adversary can trigger the deserialization routine, which then invokes malicious methods leading to Remote Code Execution (RCE). Because the polling protocol does not require authentication for the initial handshake, the attack can be launched without any prior credentials, provided the attacker has network reachability to the TeamCity server.
Observed Exploitation in the Wild
Although JetBrains has not yet disclosed the exact tactics, techniques, and procedures (TTPs) used by threat actors, CISA’s alert confirms that the vulnerability is under active exploitation. Details such as the identity of the attackers, their motivations, and the geographic scope of the campaigns remain unknown. The absence of public proof‑of‑concept code suggests that the exploits may be confined to targeted or limited‑scale operations, but the potential for broader abuse is significant given the ease of unauthenticated RCE.
Potential Impact on Affected Systems
If exploited, the vulnerability grants the attacker the same privileges as the TeamCity server process. This can lead to:
- Unauthorized read access to configuration files, project settings, and stored credentials (including SSH keys, API tokens, and database passwords).
- Modification of server state, such as altering build configurations or disabling security controls.
- Compromise of build artifacts, enabling the injection of malicious code into software supply chains.
- Lateral movement within the internal network, as the compromised TeamCity host can serve as a pivot point to other systems.
The severity of the impact depends on the service account under which TeamCity runs; running the server with elevated privileges amplifies the risk.
Mitigation and Patch Guidance
JetBrains has released security updates that address the deserialization flaw in all affected on‑premise versions. Administrators are urged to consult the official JetBrains security advisory for the exact version numbers and download links for the patches. The recommended remediation path is to upgrade to the patched release immediately; if upgrading is not feasible, applying the provided workaround—such as restricting access to the agent polling endpoint to trusted networks or disabling the polling protocol until a patch can be applied—should be considered a temporary measure.
CISA’s Binding Operational Directive (BOD) 26‑04
In response to the active exploitation, CISA has placed CVE‑2026-63077 in its Known Exploited Vulnerabilities (KEV) catalog and issued Binding Operational Directive (BOD) 26‑04. The directive mandates that all Federal Civilian Executive Branch (FCEB) agencies prioritize patching this vulnerability. Agencies must complete the required mitigations or apply the available software patches no later than August 8, 2026. Failure to comply may result in heightened scrutiny from CISA and potential reporting obligations under federal cybersecurity policies.
Broader Implications for CI/CD Security
The TeamCity incident highlights a recurring challenge in securing CI/CD platforms: the need to balance openness for agent communication with robust authentication and input validation. Organizations should adopt a defense‑in‑depth strategy that includes:
- Running CI/CD services under least‑privilege, dedicated service accounts.
- Enforcing network segmentation so that agent polling endpoints are accessible only from trusted build agent subnets.
- Implementing integrity checks and whitelisting for serialized objects, or migrating to safer communication mechanisms (e.g., mutual TLS‑authenticated APIs).
- Continuously monitoring logs for anomalous polling requests, unexpected process spawns, or privilege escalation attempts.
- Regularly reviewing and updating third‑party components to mitigate deserialization and other injection risks.
Conclusion
CVE‑2026-63077 represents a critical threat to on‑premise JetBrains TeamCity deployments, enabling unauthenticated remote code execution with potentially far‑reaching consequences for software supply chains. The confirmed active exploitation, coupled with CISA’s KEV listing and the tight BOD‑26‑04 deadline, underscores the urgency for immediate patching. Organizations must not only apply the supplied updates but also reinforce their CI/CD hardening practices to prevent similar deserialization‑based attacks in the future. By doing so, they safeguard both their internal development environments and the integrity of the software they deliver to customers.

