dbcve.org
YoutrackApplication · Jetbrains

CVE-2026-57924

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-26
Fix available
A fix is available. Upgrade to 2026.2.16593 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 8 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.2.16593 default role configuration exposed excessive user profile details

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

In JetBrains YouTrack versions prior to 2026.2.16593, the default role configuration was found to expose excessive user profile details to unauthorized users. This information disclosure vulnerability stems from overly permissive default role settings that allowed access to sensitive personal information within user profiles.

MitigationUpdate YouTrack to version 2026.2.16593 or later. After updating, audit and correct any custom role configurations to ensure they follow the principle of least privilege for user profile data access.

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:< 2026.2.16593

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Identify the installed YouTrack version
    Log into the YouTrack administration console and navigate to the About section, or access the /api/version endpoint if API access is enabled. Compare the version number against the vulnerable range: any version prior to 2026.2.16593 is affected.
    Affected if The installed version is less than 2026.2.16593
  2. Review default role configurations for user profile access
    In YouTrack administration, navigate to Access Management > Roles. Examine the default role assignments and check which roles have permissions related to viewing user profiles or user profile fields.
    Affected if Default roles grant broad visibility to user profile fields without explicit restriction
  3. Inspect user profile field visibility settings
    Go to Projects > [Select Project] > Project Settings > User Fields, or access global user field settings. Check which fields are marked as visible to users beyond the profile owner.
    Affected if Sensitive personal information fields (such as email, phone, address, or custom fields) are configured as visible to all authenticated users or to unauthorized roles
  4. Verify unauthorized user access to profile data
    Create or use a test account with minimal permissions (such as a guest or unauthenticated user if permitted) and attempt to view user profiles through the UI or API to confirm whether excessive profile details are accessible.
    Affected if Users with limited or no privileges can view personal information they should not have access to

You are affected if your YouTrack version is prior to 2026.2.16593 AND your default role configurations or user profile field settings permit unauthorized users to access sensitive personal information.

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 2026.2.16593 or later
Fixed in 2026.2.16593
Interim mitigation

Update YouTrack to version 2026.2.16593 or later. After updating, audit and correct any custom role configurations to ensure they follow the principle of least privilege for user profile data access.

Recommended fix Moderate confidence

2026.2.16593

  1. Backup your YouTrack database and configuration files before upgrading
  2. Stop the YouTrack service
  3. Download YouTrack version 2026.2.16593 or later from the official JetBrains website
  4. Run the installation or apply the upgrade package for your deployment method (standalone, Docker, or enterprise installation)
  5. Start the YouTrack service after upgrade completes
  6. Verify that the default role configuration no longer exposes excessive user profile details by reviewing role permissions in Administration > Users & Security > Roles
  7. Confirm normal functionality by testing user authentication and profile access

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

Fix this in Youtrack Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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