dbcve.org
HubApplication · Jetbrains

CVE-2026-50242

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 authentication bypass via direct database access leading to administrative access 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 · high confidence

JetBrains Hub contains an authentication bypass vulnerability allowing attackers to gain administrative access through direct database manipulation. The flaw exists in multiple versions prior to the specified patches and enables unauthorized privilege escalation without proper authentication credentials.

MitigationUpgrade JetBrains Hub to version 2026.1.13757, 2025.3.148033, 2025.2.148048, 2025.1.148120, 2024.3.148430, or 2024.2.148429 (or later). Additionally, restrict direct database access, review audit logs for suspicious administrative activity, and ensure database servers are not exposed to untrusted networks.

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 installed version
    Locate the Hub installation directory and check the version file or run 'java -jar hub.jar --version' from the installation directory. Common paths include /opt/hub or the installation path configured during setup.
    Affected if The installed version falls within any of these ranges: 2024.2.33606 to 2024.2.148429, 2024.3.44799 to 2024.3.148430, 2025.1.62455 to 2025.1.148120, 2025.2.86069 to 2025.2.148048, 2025.3.104432 to 2025.3.148033, or 2026.1.12024 to 2026.1.13757.
  2. Verify database access controls
    Review database configuration files (such as db.xml or database.properties in the Hub config directory) and confirm that the database is not exposed publicly or accessible from untrusted networks.
    Affected if The Hub database is accessible from systems other than the local Hub server, as this would enable the direct database manipulation attack vector.
  3. Inspect administrative user accounts
    Log into the Hub administration interface or query the database directly to list all users with administrative roles. Compare the list against known, expected administrator accounts.
    Affected if Any administrative account exists that was not created by your authorized administrators, or if administrative accounts appear with unexpected usernames or recent creation dates.
  4. Review database audit logs for account modifications
    Check database logs or Hub audit logs for recent INSERT, UPDATE, or DELETE operations on user or role tables, particularly those involving administrative privileges.
    Affected if Recent database modifications related to user accounts or roles are present and were not performed through the official Hub admin interface.

You are affected if your JetBrains Hub version is within any of the vulnerable version ranges listed above AND your database is accessible for direct manipulation or if unexpected administrative accounts are detected.

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, 2025.3.148033, 2025.2.148048, 2025.1.148120, 2024.3.148430, or 2024.2.148429 (or later). Additionally, restrict direct database access, review audit logs for suspicious administrative activity, and ensure database servers are not exposed to untrusted networks.

Recommended fix High confidence

2026.1.13757 or later (or the latest version in your current release branch that includes the fix: 2024.2.148429+, 2024.3.148430+, 2025.1.148120+, 2025.2.148048+, 2025.3.148033+)

  1. 1. Identify the current JetBrains Hub version by checking the Hub administration interface or the version file in the Hub installation directory
  2. 2. Based on the current version branch, plan upgrade to the corresponding fixed version: for 2024.2.x upgrade to 2024.2.148429 or later; for 2024.3.x upgrade to 2024.3.148430 or later; for 2025.1.x upgrade to 2025.1.148120 or later; for 2025.2.x upgrade to 2025.2.148048 or later; for 2025.3.x upgrade to 2025.3.148033 or later; or upgrade to the latest 2026.1.x release (2026.1.13757 or later)
  3. 3. Review JetBrains upgrade documentation for your deployment method (ZIP/war or Docker)
  4. 4. Create a backup of the Hub configuration and database before proceeding
  5. 5. Stop the Hub service
  6. 6. Perform the upgrade following JetBrains upgrade procedures for your installation type
  7. 7. Start the Hub service and verify the new version is running
  8. 8. Verify administrative authentication is working correctly and test that the vulnerability is remediated
Caveat Review JetBrains release notes for your target version to check for any breaking changes or deprecated features between your current and target version

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

Fix this in Hub Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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