CVE-2025-64681VulnerabilityPublished 10 Nov 2025

CVE-2025-64681: JetBrains Hub · CWE-862

Affects JetBrains HubSource CVE Database V5

Not known to be exploited · CVSS 2.7 Low · fixed in 2025.3.104992 : update JetBrains Hub when convenient.

Data as of 25 Oct 2026, 19:02 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 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2025.3.104992

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 10 Nov 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 2026-10-25.

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 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 Hub	Affected =0	Fixed in–

AI-suggested

1. Apply the official JetBrains Hub update to version 2025.3.104992 or later as soon as it becomes available to address the race condition. 2. Until patching is possible, restrict high-privilege user access to trusted personnel only and monitor invitation activities closely. 3. Implement additional concurrency controls or serialization mechanisms in invitation workflows to prevent simultaneous invitation processing that could trigger the race condition. 4. Enable detailed audit logging for user invitation and provisioning events to detect anomalies or suspicious patterns. 5. Review and enforce strict user limit policies at the organizational level, including manual verification of user counts periodically. 6. Educate administrators about the vulnerability and the importance of cautious handling of invitation processes. 7. Consider network segmentation or access controls to limit exposure of JetBrains Hub interfaces to reduce risk of exploitation by unauthorized actors.

Description

In JetBrains Hub before 2025.3.104992 a race condition allowed bypass of the user limit via invitations

Impact

For European organizations, the primary impact of CVE-2025-64681 lies in the potential unauthorized circumvention of user limits within JetBrains Hub. This can lead to compliance issues, especially where licensing agreements or regulatory requirements mandate strict user count controls. While confidentiality and availability remain unaffected, integrity of user management is compromised, potentially allowing unauthorized users to gain access to internal resources if user provisioning is linked to access rights. This could indirectly increase the attack surface or complicate audit and compliance efforts. Organizations with large development teams or those using Hub for critical identity management functions may face operational challenges or increased costs due to unplanned user additions. The absence of known exploits reduces immediate risk, but the vulnerability could be leveraged in insider threat scenarios or by malicious administrators. European entities with strict IT governance and compliance frameworks, such as financial institutions or government agencies, should consider the implications carefully.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
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.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (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 Nov 2025, 14:34 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats