CVE-2026-63077

CRITICAL(9.8)KEVRansomwareLikely Exploited

JetBrains TeamCity Deserialization of Untrusted Data Vulnerability

Description

CVE-2026-63077 is a critical deserialization of untrusted data vulnerability in JetBrains TeamCity that allows unauthenticated remote code execution via the agent polling protocol. All versions before 2025.11.7 and all 2026.1.x releases before 2026.1.3 are affected. TeamCity is a CI/CD server, which means it holds source code, build secrets, signing keys and deployment credentials and can push artefacts into production — taking it over gives an attacker a direct route into the software supply chain. CISA has added CVE-2026-63077 to the Known Exploited Vulnerabilities catalog and flags it as known to be used in ransomware campaigns; its EPSS score of 89.6% places it in the 99.8th percentile, and its remediation deadline of August 8, 2026 passed long ago.

KEV Information

Vendor
JetBrains
Product
TeamCity
Date Added
August 5, 2026
Due Date
August 8, 2026
Required Action
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

CVSS Score

Vector String
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HOpen in Calculator
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
Exploitability Score
3.9
Impact Score
5.9

CWEs

Affected Products

VendorProductVersion
jetbrainsteamcity< 2025.11.7; >= 2026.1, < 2026.1.3

References

Weakness Type

CWE-502: Deserialization of Untrusted Data

Deserialization of untrusted data occurs when an application reconstructs objects from a serialized stream without verifying that the result will be valid and safe. An attacker who controls the stream can cause arbitrary classes to be instantiated and dangerous operations to run during reconstruction. In TeamCity, data received over the agent polling protocol is deserialized before the sender has been authenticated, so anyone who can reach that endpoint supplies the object graph the server builds.

Learn more: CWE-502 — Deserialization of Untrusted Data

Impact Analysis

CVE-2026-63077 has a CVSS 3.1 base score of 9.8 (Critical) with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Attack Vector (Network), Privileges Required (None), User Interaction (None), Attack Complexity (Low): the agent polling endpoint must be reachable for build agents to work, and no credential or victim is involved, so exposure alone is the precondition. Confidentiality, Integrity and Availability (all High): code execution on a TeamCity server exposes VCS credentials, API tokens, signing keys and build artefacts; it allows tampering with builds that are later shipped to customers or deployed to production; and it allows destroying the build infrastructure an engineering organization depends on. Two factors make this worse than the score alone. First, CISA records this vulnerability as known to be used in ransomware campaigns, which puts the realistic outcome at encryption and extortion rather than quiet espionage. Second, the EPSS score of 89.6% in the 99.8th percentile marks it as near-certain to be attacked. The remediation deadline of August 8, 2026 is long past; any TeamCity instance still on an affected version should be handled as an incident.

Exploit Maturity

CISA has added CVE-2026-63077 to the Known Exploited Vulnerabilities catalog and marks it as known to be used in ransomware campaigns — the strongest exploitation signal the catalog carries, and one that distinguishes this entry from most others. The remediation deadline of August 8, 2026 has long passed. The EPSS score of 89.6%, in the 99.8th percentile, independently rates exploitation as near-certain. The references are JetBrains' security bulletin and the CISA catalog entry rather than exploit code, so no public proof-of-concept appears in the reference set — but for an unauthenticated Java deserialization flaw with confirmed ransomware use, the absence of a published PoC says nothing about availability. TeamCity has been targeted repeatedly in recent years, and CI/CD servers are a favoured objective because they combine high-value secrets with a trusted path into production. Patch and investigate, in that order and without delay.

Remediation

  1. Carry out the action CISA requires, immediately. Apply mitigations in accordance with JetBrains' instructions, comply with CISA's BOD 26-04 "Prioritizing Security Updates Based on Risk" guidance and the "Forensics Triage Requirements", and discontinue use of the product if mitigations are unavailable. The KEV remediation deadline of August 8, 2026 has long passed.
  2. Upgrade JetBrains TeamCity to 2025.11.7 or 2026.1.3 or later, as listed on the JetBrains security bulletin. Every release before 2025.11.7 and every 2026.1.x release before 2026.1.3 is affected, so there is no safe older build to remain on.
  3. Restrict network access to the agent polling endpoint. Until the upgrade is complete, the server should be reachable only from the networks where build agents actually run, never from the internet, and the web interface should sit behind a VPN or an authenticating proxy.
  4. Treat an exposed instance as compromised and respond accordingly. Because exploitation is unauthenticated and ransomware use is confirmed, review the server for unexpected files, scheduled build configurations, plugins and user accounts; check build history for runs that match no commit; verify backups exist offline and are restorable; and rotate every secret the server holds — VCS credentials, deployment keys, artifact repository tokens, cloud provider credentials and code signing keys.
  5. Consider shipped artefacts as well, and harden deserialization generally. If compromise is suspected, verify the integrity of artefacts built during the exposure window before trusting them downstream. For software you maintain, avoid deserializing untrusted input altogether, prefer text formats such as JSON, apply integrity checks to serialized data, and restrict deserializable classes with an allowlist — and always authenticate before deserializing anything.

Technical Details

TeamCity's agent polling protocol exists so that build agents can contact the server for work, and in affected versions the server deserializes the data it receives on that channel before establishing that the sender is a legitimate agent. That ordering is the defect: deserialization reconstructs objects and executes code paths as part of reconstruction, so performing it ahead of authentication hands an unauthenticated attacker control over which objects the server builds — the CWE-502 mechanism. Java deserialization gadget chains turn that control into arbitrary code execution with the privileges of the TeamCity process, which on a CI/CD server is an identity with broad access to repositories, artifact stores and deployment targets. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H records the complete absence of preconditions, with full impact across confidentiality, integrity and availability and an unchanged scope — the authority gained is the server's own, which in a build pipeline is precisely the authority that signs and deploys.

Frequently Asked Questions

Is CVE-2026-63077 being actively exploited?

Yes, and more specifically than usual: CISA has added CVE-2026-63077 to the Known Exploited Vulnerabilities catalog and flags it as known to be used in ransomware campaigns. The remediation deadline of August 8, 2026 has long passed, and the EPSS score of 89.6% places the vulnerability in the 99.8th percentile, indicating near-certain exploitation activity.

What products are affected by CVE-2026-63077?

CVE-2026-63077 affects JetBrains TeamCity in all versions before 2025.11.7 and in the 2026.1 line before 2026.1.3. The vulnerable component is the server's agent polling protocol, so the TeamCity server is the affected system; build agents are the legitimate users of the protocol rather than the vulnerable party.

How do I fix CVE-2026-63077?

Upgrade TeamCity to 2025.11.7 or 2026.1.3 or later per the JetBrains security bulletin. Because the deadline has long passed and ransomware use is confirmed, also restrict network access to the server, verify that offline backups exist and restore cleanly, review the server for unexpected plugins, users and build configurations, and rotate VCS credentials, deployment keys, artifact tokens and code signing keys.

How severe is CVE-2026-63077?

CVE-2026-63077 is rated Critical with a CVSS 3.1 base score of 9.8: unauthenticated remote code execution with no user interaction and complete impact on confidentiality, integrity and availability. Its EPSS score of 89.6% is in the 99.8th percentile, and CISA records known use in ransomware campaigns. Because a CI/CD server holds signing keys and deploys to production, successful exploitation is a supply chain compromise, not merely a server compromise.

CVSS Score

9.8
CRITICAL(9.8)

EPSS Score

EPSS Score94.89%
EPSS Percentile99.9%

Dates

PublishedJuly 27, 2026
Last ModifiedOctober 24, 2026
StatusAnalyzed
CVSS Versionv3.1

Need Help With Vulnerability Management?

Our security experts can help you prioritize and remediate vulnerabilities effectively.