Skip to content

Project

TeamCity

TeamCity is a JetBrains continuous integration and delivery (CI/CD) server used to automate building, testing, and deploying software.

Known aliases

  • JetBrains TeamCity
  • JetBrains TeamCity Blog
  • TeamCity
  • TeamCity On-Premises

Current stories

securityOne report1 publisher

JetBrains' final Cadence update moves the exposure from a 2024 backup into live storage

The September 3 note closed the investigation without adding a single affected user, but it put project source code and credentials in current Cadence storage inside a blast radius that had been limited to a 2024 backup.

Reality

Evidence64
Adoption42
Hype gap−22
Incentives78
Confidence61
securityOne report1 publisher

Unpatched TeamCity server gave attackers AWS IAM credentials from JetBrains' Cadence backup

CVE-2026-63077 was in CISA's KEV catalog on August 5. JetBrains dates the intrusion into its own Cadence environment from August 8 to August 24, and every secret that touched the service now needs rotating.

Reality

Evidence62
Adoption38
Hype gap−8
Incentives66
Confidence64
buildOne report1 publisher

GitHub's runner cuts drop the 64-core arm64 box to $5.88 an hour

The reductions run deepest on the largest machines. That redoes the arithmetic that sent heavy jobs to hardware you own. The per-minute charge GitHub proposed for self-hosted runners still has no new date.

Publishers:dev.to

Reality

Evidence58
Adoption52
Hype gap+10
Incentives72
Confidence57
buildOne report1 publisher

TeamCity's new OIDC plugin turns your build server into the credential issuer

Build configurations can now authenticate to AWS and Google Cloud without stored keys, provided you accept that the TeamCity server holds the signing key and that rotating it leaves already-issued tokens valid.

Reality

Evidence46
Adoption12
Hype gap+14
Incentives82
Confidence56
buildOne report1 publisher

An exposed Java debug port on a CI server was exploited within hours

Wiz says a TeamCity honeypot exposing JDWP was mining Monero within hours, and GreyNoise counted more than 6,000 unique IPs scanning for the protocol in 90 days.

Publishers:wiz.io

Reality

Evidence63
Adoption52
Hype gap+12
Incentives70
Confidence58