VulnerabilityPublished 11 Dec 2025

CVE-2025-67739: JetBrains TeamCity · CWE-939

Affects JetBrains TeamCitySource CVE Database V5

Not known to be exploited · CVSS 3.1 Low.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

3.1Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
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: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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 11 Dec 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 updating JetBrains TeamCity installations to version 2025.11.2 or later, where the vulnerability is fixed. Until patched, restrict network access to TeamCity servers to trusted IPs and enforce strict access controls to limit low-privilege user capabilities. Implement network segmentation to isolate CI/CD infrastructure from broader enterprise networks. Conduct regular audits of TeamCity configurations and repository URL inputs to detect anomalous or malformed entries. Employ monitoring and alerting on unusual repository URL requests or access patterns that could indicate exploitation attempts. Educate development and operations teams about the risks of exposing internal paths and encourage secure coding and configuration practices. Finally, maintain an incident response plan that includes reconnaissance activity detection to quickly respond if information leakage is suspected.

Description

In JetBrains TeamCity before 2025.11.2 improper repository URL validation could lead to local paths disclosure

Impact

For European organizations, the primary impact is the potential leakage of internal directory structures and repository paths from TeamCity servers. While this does not directly compromise data integrity or system availability, it can provide attackers with valuable intelligence to plan more sophisticated attacks, such as privilege escalation or targeted malware deployment. Organizations heavily reliant on TeamCity for software development and deployment, especially those integrating with multiple repositories, may face increased risk of information exposure. This could be particularly sensitive in sectors like finance, healthcare, or critical infrastructure where internal architecture confidentiality is paramount. The vulnerability's low severity and lack of known exploits reduce immediate risk, but unpatched systems could be leveraged in multi-stage attacks. Additionally, the exposure of local paths might reveal naming conventions or environment details that facilitate social engineering or insider threats.

CWE-939Improper Authorization in Handler for Custom URL Scheme (opens in a new tab)
Base weakness
The product uses a handler for a custom URL scheme, but it does not properly restrict which actors can invoke the handler using the scheme.
Architecture and Design
Utilize a user prompt pop-up to authorize potentially harmful actions such as those modifying data or dealing with sensitive information.
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V1.14.1 (opens in a new tab)
V13.4.2 (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 11 Dec 2025, 15:54 UTC

WeaknessesCWE-939

Technical details

References

Community reviews

Related threats