dbcve.org
HubApplication · Jetbrains

CVE-2025-64683

HIGH · 7.5 CVSS v3.1 Published 2025-11-10
Fix available
A fix is available. Upgrade to 2025.3.104432 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In JetBrains Hub before 2025.3.104432 information disclosure was possible via the Users API

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

JetBrains Hub before version 2025.3.104432 contains an information disclosure vulnerability in the Users API that allows unauthorized access to sensitive user information. The specific user data exposed and the exact attack vector are not detailed in the available description, but the CVSS 7.5 score indicates this is a significant information exposure issue, likely exploitable without authentication or with low-privilege access.

MitigationUpgrade JetBrains Hub to version 2025.3.104432 or later to remediate this vulnerability. As this is a single-component patch update, the fix is straightforward but should be tested to ensure the upgrade does not introduce regressions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
HubApplication
Affected:< 2025.3.104432

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine JetBrains Hub installation version
    Locate the Hub installation directory and check the version file or startup logs. Common locations include /opt/hub, the installation root, or the hub startup banner. Run 'hub --version' if the CLI is available, or check the 'version' file in the Hub distribution.
    Affected if The installed version is lower than 2025.3.104432 (e.g., 2025.3.x before build 104432, or any earlier major/minor version).
  2. Verify the Users API endpoint is accessible
    Identify the base URL for your Hub instance (e.g., https://hub.yourcompany.com). Attempt to access the Users API endpoint, typically at /api/users or /rest/users, without providing authentication credentials.
    Affected if The API responds with user data (JSON containing user profiles, emails, names, or other sensitive fields) without requiring authentication or returning a 401/403 error.
  3. Inspect API response for sensitive fields
    Send a GET request to the users endpoint and examine the returned payload. Look for exposure of fields such as email addresses, full names, user IDs, roles, or internal profile information that should require authorization.
    Affected if The response contains sensitive user PII or internal data that should be restricted to authenticated administrators only.
  4. Review access control configuration
    Check Hub's security configuration files or admin settings for the Users API endpoint. Verify whether anonymous or low-privilege access is permitted to user data endpoints.
    Affected if Anonymous access is enabled or unauthenticated requests successfully retrieve user data from the API.

Your environment is affected if JetBrains Hub is installed at any version below 2025.3.104432 and the Users API endpoint returns sensitive user information without requiring authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2025.3.104432 or later
Fixed in 2025.3.104432
Interim mitigation

Upgrade JetBrains Hub to version 2025.3.104432 or later to remediate this vulnerability. As this is a single-component patch update, the fix is straightforward but should be tested to ensure the upgrade does not introduce regressions.

Recommended fix High confidence

2025.3.104432

  1. Back up the current Hub installation and database before upgrading
  2. Download JetBrains Hub version 2025.3.104432 or later from the official JetBrains website
  3. Stop the running Hub service
  4. Install the new version following the standard Hub upgrade procedure
  5. Restart the Hub service
  6. Verify the Users API no longer exposes sensitive information and that the race condition is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Hub Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64683 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64683 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data