Check exposure:TeamCity CVE-2024-27198: Auth Bypass Used by Ransomware. Owners of self-hosted TeamCity servers that ran 2023.11.3 or older without the security patch plugin at any point after March 4, 2024, especially internet-facing ones.
Check exposure:TeamCity CVE-2024-27199: Path Traversal Joins KEV in 2026. Owners of self-hosted TeamCity servers still on 2023.11.3 or older, servers patched only with the 2024 plugin, and anyone whose server was internet-facing and unpatched in early March 2024.
Do you run any of these? Microsoft Windows. They are being exploited in the wild (CISA KEV). Patch or mitigate if you do; CISA’s federal deadline is 2024-03-25.
npm: 1 critical advisory (jsonata). Check with npm audit (or: npm ls <package>).
Go: 1 critical advisory (github.com/zeromicro/go-zero). Check with govulncheck ./....
None of it touches your stack? Then there is nothing to do today. That is a result, not a failure to read carefully.
Any TeamCity server that was internet-reachable and below 2023.11.4 in March 2024 may have been taken over; upgrade to a current release (which also fixes 2026's CVE-2026-63077) and audit for rogue admins and plugins.
Must act: Owners of self-hosted TeamCity servers that ran 2023.11.3 or older without the security patch plugin at any point after March 4, 2024, especially internet-facing ones.
Can relax: TeamCity Cloud customers, whom JetBrains patched and says were not attacked, and on-prem servers that were patched promptly and are now on a current release.
Check the TeamCity version on every self-hosted server (shown in the web UI footer and under Administration).
Upgrade to a current TeamCity release; 2023.11.4 fixes this bug, but 2025.11.7 or 2026.1.3 and later are needed for 2026's CVE-2026-63077.
Keep the TeamCity web UI off the internet or behind a VPN or SSO proxy.
Fixed since March 2024 alongside a critical sibling; confirm no TeamCity server is still on 2023.11.3 or older, move everything to a build that also fixes CVE-2026-63077, and hunt on servers that were exposed and unpatched in March 2024.
Must act: Owners of self-hosted TeamCity servers still on 2023.11.3 or older, servers patched only with the 2024 plugin, and anyone whose server was internet-facing and unpatched in early March 2024.
Can relax: TeamCity Cloud customers, and on-prem teams that upgraded in March 2024, are now on 2025.11.7, 2026.1.3 or later, and do not expose the server publicly.
Inventory every TeamCity On-Premises server and record its version from the web UI footer or GET /app/rest/server.
Upgrade anything older than 2025.11.7 or 2026.1.3 to a current release; the 2024 patch plugin covers only the March 2024 bugs.
Remove direct internet exposure: put TeamCity behind a VPN or an IP allowlist.