dbcve.org
HubApplication · Jetbrains

CVE-2026-56141

CRITICAL · 9.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 →
100/100
Remediation priority · Urgent
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 2026.1.13757, 2025.3.148033, 2025.2.148048, 2025.1.148120, 2024.3.148430, 2024.2.148429 account takeover via predictable restore codes 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

Account takeover vulnerability in JetBrains Hub where restore codes used for account recovery were predictable rather than cryptographically random. Attackers could potentially guess valid restore codes to gain unauthorized access to user accounts.

MitigationUpgrade JetBrains Hub to version 2026.1.13757 or later, or to one of the patched versions (2025.3.148033+, 2025.2.148048+, 2025.1.148120+, 2024.3.148430+, 2024.2.148429+). Review audit logs for suspicious account recovery activity.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 version
    Locate the Hub installation and check the version file or use the Hub admin interface to view the version information. Typical locations include the Hub installation directory or the application's 'About' section in the admin console.
    Affected if The installed version falls within one of these 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. Confirm account recovery feature is enabled
    Verify that the account recovery or password reset functionality using restore codes is active for users in this Hub instance. This is typically enabled by default but can be confirmed through Hub admin settings under user authentication or account recovery options.
    Affected if Restore codes are enabled for account recovery in this Hub deployment.

You are affected if your JetBrains Hub version is within any of the vulnerable version ranges listed AND restore codes are enabled for user account recovery.

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 to one of the patched versions (2025.3.148033+, 2025.2.148048+, 2025.1.148120+, 2024.3.148430+, 2024.2.148429+). Review audit logs for suspicious account recovery activity.

Recommended fix High confidence

Upgrade to 2026.1.13757 or later (or at minimum the patched version for your release line: 2024.2.148429, 2024.3.148430, 2025.1.148120, or 2025.2.148048)

  1. 1. Identify the current Hub version using the Hub admin interface or command line
  2. 2. Based on the current version line, determine the appropriate upgrade target: for 2024.2.x go to >=2024.2.148429, for 2024.3.x go to >=2024.3.148430, for 2025.1.x go to >=2025.1.148120, for 2025.2.x go to >=2025.2.148048
  3. 3. Download the appropriate Hub upgrade package from jetbrains.com
  4. 4. Follow JetBrains standard upgrade procedure: stop the Hub service, backup the Hub configuration and data directories, deploy the new version, start the Hub service
  5. 5. Verify the upgrade was successful by checking the Hub version in the admin interface
  6. 6. Confirm the vulnerability is resolved by attempting an account restore flow to verify the restore codes are now unpredictable
Caveat Review JetBrains release notes for your target version for any breaking changes or migration requirements

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

Fix this in Hub Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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