dbcve.org
YoutrackApplication · Jetbrains

CVE-2026-62422

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-14
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 5 weeks old

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 YouTrack 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 YouTrack allows authentication bypass via direct database access, enabling an attacker to gain administrative privileges without valid credentials. The vulnerability exists in multiple older versions across the 2024-2025 release trains.

MitigationUpgrade YouTrack to version 2026.1.13757, 2025.3.148033, 2025.2.148048, 2025.1.148120, 2024.3.148430, or 2024.2.148429 or later. Restrict direct database access as a defense-in-depth measure.

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
YoutrackApplication
Affected:< 2024.2.148429>= 2024.3.44799, < 2024.3.148430>= 2025.1.62455, < 2025.1.148120>= 2025.2.86069, < 2025.2.148048>= 2025.3.87341, < 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. Determine if direct database access is enabled
    Inspect your YouTrack database configuration and network settings. Check if the database server (PostgreSQL, MySQL, or internal) is accessible from untrusted networks or if direct connections are allowed beyond the application server.
    Affected if Direct database connections are permitted from network locations outside the YouTrack application server itself
  2. Identify installed YouTrack version
    Log into YouTrack as an administrator and navigate to Administration > About, or check the <youtrack_install_dir>/versions.json file if you have file system access.
    Affected if The installed version is earlier than 2024.2.148429, 2024.3.148430, 2025.1.148120, 2025.2.148048, 2025.3.148033, or 2026.1.13757
  3. Verify database user privileges
    Review the database user account configured for YouTrack. Check if this account has elevated privileges beyond what the application requires, or if it has administrative-level permissions on the database.
    Affected if The YouTrack database user possesses administrative or superuser privileges on the database server

A user is affected if they are running a YouTrack version earlier than the fixed releases AND direct database access is possible from their 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 YouTrack to version 2026.1.13757, 2025.3.148033, 2025.2.148048, 2025.1.148120, 2024.3.148430, or 2024.2.148429 or later. Restrict direct database access as a defense-in-depth measure.

Recommended fix High confidence

YouTrack 2026.1.13757 or later

  1. 1. Back up your YouTrack database and configuration before upgrading.
  2. 2. Download JetBrains YouTrack 2026.1.13757 or later from the official JetBrains website (www.jetbrains.com/youtrack/download).
  3. 3. Stop the YouTrack service on your server.
  4. 4. Install the new version following JetBrains standard upgrade procedures.
  5. 5. Restart the YouTrack service.
  6. 6. Verify that authentication is now required for administrative access and direct database access no longer bypasses authentication.
Caveat Review JetBrains release notes for any changes in functionality between your current version and 2026.1.13757

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

Fix this in Youtrack Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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