VulnerabilityPublished 17 Sep 2025

CVE-2025-59457: JetBrains TeamCity · CWE-183

Affects JetBrains TeamCitySource CVE Database V5

Not known to be exploited · CVSS 7.7 High · fixed in 2025.07.2 : patch JetBrains TeamCity soon.

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.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2025.07.2

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
JetBrains TeamCity	Affected =0	Fixed in–

AI-suggested

European organizations should prioritize upgrading JetBrains TeamCity installations to version 2025.07.2 or later as soon as possible to remediate this vulnerability. Until patching is complete, organizations should implement strict network segmentation to limit access to TeamCity servers, especially restricting access to trusted administrators and build agents only. Review and rotate any Git credentials or tokens used by TeamCity to prevent misuse of potentially leaked credentials. Implement monitoring and alerting for unusual Git repository access patterns or authentication failures. Employ application-layer firewalls or endpoint detection solutions to detect anomalous requests targeting TeamCity Git URL handling. Additionally, enforce the principle of least privilege on TeamCity service accounts and audit their permissions regularly. Consider temporarily disabling Git repository integrations on Windows TeamCity servers if feasible until patches are applied. Finally, maintain up-to-date backups of CI/CD configurations and credentials to enable rapid recovery if compromise is detected.

Description

In JetBrains TeamCity before 2025.07.2 missing Git URL validation allowed credential leakage on Windows

Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality of sensitive development credentials and potentially the source code itself. Many European enterprises rely on JetBrains TeamCity for their CI/CD workflows, especially in software development, financial services, manufacturing, and telecommunications sectors. Credential leakage could lead to unauthorized access to private Git repositories, enabling intellectual property theft, insertion of malicious code, or further lateral movement within corporate networks. Given the vulnerability affects Windows-based TeamCity servers, organizations running these environments are particularly at risk. The compromise of CI/CD credentials can disrupt development pipelines and erode trust in software integrity, which is critical for compliance with European regulations such as GDPR and NIS Directive. Additionally, the exposure of credentials could facilitate supply chain attacks, which have become a growing concern in Europe. The absence of known exploits in the wild currently provides a window for mitigation, but the high CVSS score and ease of exploitation warrant urgent attention.

CWE-183Permissive List of Allowed Inputs (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are explicitly allowed by policy because the inputs are assumed to be safe, but the list is too permissive - that is, it allows an input that is unsafe, leading to resultant weaknesses.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
Attack patterns
Double Encoding (opens in a new tab)
Using Leading 'Ghost' Character Sequences to Bypass Input Filters (opens in a new tab)
Exploiting Multiple Input Interpretation Layers (opens in a new tab)
Using Unicode Encoding to Bypass Validation Logic (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

jetbrains.com/privacy-security/issues-fixed/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Sep 2025, 13:15 UTC

WeaknessesCWE-183

Technical details

References

Community reviews

Related threats