dbcve.org
HubApplication · Jetbrains

CVE-2026-56142

HIGH · 8.8 CVSS v3.1 Published 2026-06-19
Fix available
A fix is available. Upgrade to 2024.2.148429 / 2024.3.148430 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 2026.1.13757, 2025.3.148033, 2025.2.148048, 2025.1.148120, 2024.3.148430, 2024.2.148429 privilege escalation by attaching authentication details to accounts was possible

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

This is a privilege escalation vulnerability in JetBrains Hub where attackers could attach authentication details to accounts, allowing them to gain elevated privileges beyond what their account should normally permit. The flaw exists in the account management/authorization logic prior to the patched versions.

MitigationUpgrade JetBrains Hub to version 2026.1.13757 or later (or one of the interim fixed versions: 2025.3.148033, 2025.2.148048, 2025.1.148120, 2024.3.148430, 2024.2.148429) to remediate this vulnerability.

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:>= 2024.2.33606, < 2024.2.148429>= 2024.3.44799, < 2024.3.148430>= 2025.1.62455, < 2025.1.148120>= 2025.2.86069, < 2025.2.148048>= 2025.3.104432, < 2025.3.148033>= 2026.1.12024, < 2026.1.13757

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify JetBrains Hub installation
    Locate the Hub installation directory and check for version information. This is typically visible in the Hub admin dashboard under 'About' or 'System Info', or check the hub installation logs or version file in the installation directory.
    Affected if The Hub version falls within any of the affected ranges: 2024.2.33606 to 2024.2.148428, 2024.3.44799 to 2024.3.148429, 2025.1.62455 to 2025.1.148119, 2025.2.86069 to 2025.2.148047, 2025.3.104432 to 2025.3.148032, or 2026.1.12024 to 2026.1.13756.
  2. Determine if account management interface is accessible
    Verify that the Hub instance has user management or account administration features enabled and accessible. This includes checking if the '/admin/users' or similar account management endpoints are available.
    Affected if The account management or user administration interface is exposed and the installed version is within the affected ranges.
  3. Check authorization configuration
    Review the Hub authorization and authentication settings to confirm that non-admin users can potentially modify or attach authentication details to accounts.
    Affected if The authorization configuration allows regular users or unprivileged accounts to access account management functions, and the version is affected.

You are affected if your installed JetBrains Hub version matches any of the vulnerable version ranges and the account management/authorization features are accessible in your environment.

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 2024.2.148429 / 2024.3.148430 / 2025.1.148120 or later
Fixed in 2024.2.1484292024.3.1484302025.1.148120
Interim mitigation

Upgrade JetBrains Hub to version 2026.1.13757 or later (or one of the interim fixed versions: 2025.3.148033, 2025.2.148048, 2025.1.148120, 2024.3.148430, 2024.2.148429) to remediate this vulnerability.

Recommended fix High confidence

2026.1.13757 (or appropriate branch fix: 2024.2.148429, 2024.3.148430, 2025.1.148120, 2025.2.148048, or 2025.3.148033)

  1. 1. Back up the current Hub installation and database
  2. 2. Download the latest stable JetBrains Hub version (2026.1.13757 or the appropriate fixed version for your branch) from the official JetBrains website
  3. 3. Stop the Hub service
  4. 4. Install the updated Hub version following the standard upgrade procedure
  5. 5. Verify the service starts successfully
  6. 6. Test that authentication and user account management work correctly
  7. 7. Confirm the privilege escalation vulnerability is resolved by verifying that unprivileged users cannot attach authentication details to other accounts
Caveat Review JetBrains Hub release notes for your upgrade path for any potential compatibility or configuration changes

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

Fix this in Hub Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56142 — 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-2026-56142 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