JetBrains TeamCity
CVE-2026-63077: unauthenticated code execution in the TeamCity agent protocol.
In JetBrains TeamCity before 2026.1.3 and 2025.11.7, unauthenticated remote code execution was possible through the agent polling protocol. CISA lists it as exploited and records known ransomware campaign use.
Exploitation
- Exploitation
- Exploited in the wild
- CISA KEV
- Listed 5 Aug 2026
- Federal due date 8 Aug 2026; catalogue read 31 Oct 2026
- EPSS
- 94% in 30 days
- Percentile 100%, scored 29 Oct 2026
- 9.8Critical, (CVSS 3.1)Scored by NVD
- 94%EPSS, chance of exploitation in 30 daysPercentile 100%; scored 29 Oct 2026
- 27 JulPublished by NVD27 Jul 2026; record read 24 Oct 2026
Versions
Affected and fixed.
.
| Affected | Fixed in |
|---|---|
| TeamCity before 2025.11.7 | 2025.11.7 |
| TeamCity before 2026.1.3 | 2026.1.3 |
What to do now
Upgrade every TeamCity server to 2026.1.3 or 2025.11.7 and review the build history for runs that were not yours. The list sits in our digest.
How to check exposure
The server version prints in the TeamCity administration area and on its sign-in page. Releases before 2026.1.3 on the current line and before 2025.11.7 on the previous line are affected; the JetBrains fixed security issues page, referenced from the NVD record, lists the fix. The NVD configuration ends the affected ranges at those two releases.
The agent polling protocol is the channel build agents use to reach the server, so a server whose agent port is open to the internet is exposed to anyone.
Who this reaches in Australia
TeamCity builds and deploys the software of Australian engineering teams, and a build server holds the secrets that deploy to production. Code execution there is a supply chain position: every artefact the server ships afterwards is suspect, which is why the ransomware use matters.
Under the Essential Eight the fix is patch applications for an internet-facing service within 48 hours. For software we build and host, the delivery pipeline is treated as production and patched on the same windows.
Timeline
Disclosed, published, listed, advised.
- : Published by NVD
- : Added to the CISA Known Exploited Vulnerabilities Catalog
- : CISA due date for US federal agencies
- : NVD record last modified
Questions, answered.
Is CVE-2026-63077 exploited?
Yes. CISA added it to the Known Exploited Vulnerabilities Catalog on 5 August 2026 with an 8 August due date and records known use in ransomware campaigns. The EPSS score is near the top of the scale.
Which releases fix it?
TeamCity 2026.1.3 and 2025.11.7, as the NVD description states. the JetBrains fixed security issues page carries the detail.
What should a team check after patching?
The build and deployment history for runs nobody started, the secrets the server holds and the artefacts it published since the exposure began. A build server compromise reaches whatever it deployed.
Provenance
Sources, and when they were read.
Every source was read 31 Oct 2026.
- 1NVD, CVE-2026-63077NIST. US Government work, public domain.
- 2CISA, Known Exploited Vulnerabilities CatalogUS Government work, public domain.
- 3FIRST, EPSS score for CVE-2026-63077EPSS terms of use.
- 4Black Shard, Essential Eight assessment
- 5Black Shard, Exploited in August and September 2026: 74 flaws added, from SharePoint to RouterOS
