JetBrains s.r.o.

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability. It refers to the loss of availability of the impacted component itself, such as a networked service (e.g., web, database, email). Since availability refers to the accessibility of information resources, attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of an impacted component.

Availability

There is no impact to availability within the impacted component.

None

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability. Such conditions may require the collection of more information about the target or computational exceptions. The assessment of this metric excludes any requirements for user interaction in order to exploit the vulnerability. If a specific configuration is required for an attack to succeed, the Base metrics should be scored assuming the vulnerable component is in that configuration.

Attack Complexity

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.

This metric reflects the context by which vulnerability exploitation is possible. The Base Score increases the more remote (logically, and physically) an attacker can be in order to exploit the vulnerable component.

Attack Vector

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).

Network

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones.

Confidentiality

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.

High

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

Integrity

There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

Privileges Required

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.

Does a successful attack impact a component other than the vulnerable component? If so, the Base Score increases and the Confidentiality, Integrity and Authentication metrics should be scored relative to the impacted component.

Scope

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.

Changed

This metric captures the requirement for a user, other than the attacker, to participate in the successful compromise the vulnerable component. This metric determines whether the vulnerability can be exploited solely at the will of the attacker, or whether a separate user (or user-initiated process) must participate in some manner.

User Interaction

The vulnerable system can be exploited without any interaction from any user.

Metasploit Framework

ProjectDiscovery nuclei-templates

Exploit-DB

CVE Program CNA list

FIRST CVSS v3.1

FIRST CVSS v4.0

CVE-2025-64689 is a vulnerability identified in JetBrains YouTrack, a widely used issue tracking and project management software. The vulnerability has a CVSS 3.1 vector of AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N, indicating that it is remotely exploitable over the network with low attack complexity and requires low privileges but no user interaction. The scope is changed, meaning the vulnerability affects resources beyond the initially vulnerable component. The impact on confidentiality and integrity is high, while availability is not affected. This suggests that an attacker with low-level access could escalate privileges or manipulate data, potentially gaining unauthorized access to sensitive project information or altering issue tracking data. No affected versions or patches have been specified yet, and no known exploits are reported in the wild. The vulnerability was reserved and published in November 2025 by JetBrains, indicating recent discovery. The lack of detailed technical information limits precise exploitation methods, but the CVSS vector implies a critical security flaw that could be leveraged in targeted attacks or insider threat scenarios.

CVE Database V5

Detailed information about CVE-2025-64689: CWE-522 in JetBrains YouTrack affecting JetBrains YouTrack. Get real-time updates, technical details, and mitigation 

CVE-2025-64689 has been rejected

Official rejection reason