Skip to main content
VulnerabilityPublished Updated

CVE-2025-54531: JetBrains TeamCity · CWE-23

Affects JetBrains TeamCitySource CVE Database V5

0

Not known to be exploited · CVSS 7.7 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
JetBrains TeamCityAffected
  • =0
Fixed in–

AI-suggested

  1. Upgrade TeamCity to version 2025.07 or later once patches are released by JetBrains to address this vulnerability.
  2. Until patches are available, restrict plugin installation permissions strictly to trusted administrators to minimize the risk of malicious plugin unpacking.
  3. Implement strict file system monitoring and integrity checks on directories used by TeamCity for plugin unpacking to detect unauthorized file modifications.
  4. Employ application whitelisting and endpoint protection solutions to prevent execution or loading of unauthorized files.
  5. Enforce the principle of least privilege for users with access to TeamCity servers, limiting elevated privileges only to essential personnel.
  6. Educate administrators about the risks of social engineering attacks that could lead to user interaction triggering exploitation.
  7. Consider isolating TeamCity build agents and servers in segmented network zones to reduce lateral movement in case of compromise.
  8. Regularly audit and review plugin sources and verify digital signatures where applicable to ensure plugin authenticity.

Description

In JetBrains TeamCity before 2025.07 path traversal was possible via plugin unpacking on Windows

References

Community reviews

Loading reviews…