VulnerabilityPublished 16 Dec 2025

CVE-2025-68162: JetBrains TeamCity · Untrusted Functionality Inclusion

Affects JetBrains TeamCitySource CVE Database V5

Not known to be exploited · CVSS 2.7 Low.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score

2.7Low

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
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: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
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: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 16 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

Upgrade to JetBrains TeamCity version 2025.11 or later as soon as the patch becomes available to eliminate the vulnerability.
Restrict high privilege accounts to only trusted personnel and enforce the principle of least privilege to minimize the number of users who can exploit this flaw.
Implement rigorous access controls and multi-factor authentication (MFA) for all users with elevated privileges in TeamCity.
Audit existing project configurations to identify and remove any unauthorized or suspicious Maven extensions or plugins.
Monitor build logs and extension loading activities for anomalies that could indicate exploitation attempts.
Employ network segmentation to isolate CI/CD infrastructure from less trusted networks and systems.
Educate development and DevOps teams about the risks of loading untrusted extensions and enforce policies to validate third-party components.
Maintain an incident response plan that includes scenarios involving CI/CD pipeline compromise to enable rapid containment and remediation.

Description

CVE-2025-68162 is a low-severity vulnerability in JetBrains TeamCity versions before 2025.11, involving the Maven embedder's ability to load extensions via project configuration. This CWE-829 weakness allows an attacker with high privileges to load potentially malicious extensions, leading to integrity impacts without affecting confidentiality or availability. Exploitation requires authenticated access with high privileges and no user interaction. Although the CVSS score is low (2.7), the vulnerability could allow unauthorized modification of build processes or configurations. No known exploits are currently reported in the wild. European organizations using TeamCity for CI/CD pipelines should review their access controls and update to the fixed version once available. Countries with significant software development industries and widespread TeamCity adoption are more likely to be impacted. Mitigations include restricting high privilege accounts, auditing project configurations, and monitoring for unusual extension loads.

Impact

For European organizations, the primary impact of CVE-2025-68162 lies in the potential compromise of software build integrity. Organizations relying on TeamCity for their CI/CD pipelines could face risks of unauthorized code injection or modification if an attacker with high privileges exploits this vulnerability. While confidentiality and availability are not directly affected, the integrity breach could lead to downstream security issues, including deployment of malicious or altered software to production environments. This is particularly critical for sectors with stringent software assurance requirements such as finance, healthcare, and critical infrastructure. The requirement for high privilege access limits the attack surface but emphasizes the importance of strict access control and monitoring. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits post-disclosure. European organizations with mature DevOps practices and automated pipelines using TeamCity should prioritize assessment and remediation to prevent potential supply chain compromises.

Summary

CVE-2025-68162 is a vulnerability identified in JetBrains TeamCity, a popular continuous integration and delivery (CI/CD) server, affecting versions prior to 2025.11. The issue stems from the Maven embedder component, which improperly allows loading of extensions through project configuration files. This behavior corresponds to CWE-829, which involves inclusion of functionality from untrusted control of a resource or configuration. An attacker with high privileges—meaning they have authenticated access with elevated rights—can exploit this flaw to load arbitrary extensions. These extensions could modify the build process or introduce malicious code, thereby compromising the integrity of the CI/CD pipeline. The CVSS v3.1 base score is 2.7, reflecting a low severity primarily because exploitation requires high privilege and no confidentiality or availability impact is observed. No user interaction is needed, and the scope remains unchanged, indicating the vulnerability affects only the vulnerable component without extending to other system components. No public exploits have been reported, and no patches are currently linked, suggesting this is a recently disclosed vulnerability. The technical details confirm the vulnerability was reserved and published on December 16, 2025. Given TeamCity’s role in automating software builds and deployments, integrity compromises here could lead to unauthorized code changes or supply chain risks if exploited.

CWE-829Inclusion of Functionality from Untrusted Control Sphere (opens in a new tab)
Base weaknessOWASP Top 10 A08:2025: Software or Data Integrity Failures (opens in a new tab)
The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Vulnerable Dependency Management (opens in a new tab)
Software Supply Chain Security (opens in a new tab)
Infrastructure as Code (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.6 (opens in a new tab)
V14.2.3 (opens in a new tab)
V14.2.4 (opens in a new tab)
Attack patterns
Serialized Data External Linking (opens in a new tab)
DTD Injection (opens in a new tab)
Local Code Inclusion (opens in a new tab)
PHP Local File Inclusion (opens in a new tab)
Remote Code Inclusion (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 23 Dec 2025, 15:58 UTC

WeaknessesCWE-829

Technical details

References

Community reviews

Related threats