CVE-2026-57925
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 · uneditedIn JetBrains YouTrack before 2026.2.16593 improper access control allowed reading saved queries and tags
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 confidenceIn JetBrains YouTrack before version 2026.2.16593, an improper access control vulnerability allowed unauthorized users to read saved queries and tags that should have been restricted based on permissions. This is a confidentiality-focused flaw where the application failed to properly validate user authorization before granting access to sensitive query and tag data.
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< 2026.2.16593CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify YouTrack versionLocate the installed YouTrack version number. In the web interface, this is typically shown in the footer of any page or accessible via Administration > System > About. If using a self-hosted installation, check the youtrack.jar or service version information.Affected if The version is below 2026.2.16593 (for example, 2026.2.16592 or earlier)
-
Confirm saved queries or tags existCheck if any projects contain saved searches or custom tags. Navigate to a project and look for saved queries in the search sidebar or tags in the project settings. These are the data objects referenced in the vulnerability.Affected if There are saved queries or custom tags with restricted visibility settings in any project
-
Review permission boundariesIn YouTrack administration, examine the permission scheme for users or groups with restricted access. Specifically check if there are users assigned to roles that should limit visibility of certain queries or tags.Affected if Users with limited roles exist alongside saved queries or tags that should be restricted to higher-privilege users only
You are affected if YouTrack is version 2026.2.16593 or lower AND saved queries or tags with permission restrictions are present in the instance.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2026.2.16593
Upgrade YouTrack to version 2026.2.16593 or later to obtain the patched version with corrected access control checks. After upgrading, verify that users can only access saved queries and tags they are explicitly permitted to view.
2026.2.16593 or later
- 1. Back up your YouTrack database before starting the upgrade process
- 2. Download YouTrack version 2026.2.16593 or later from the official JetBrains website
- 3. Stop the YouTrack service
- 4. Run the upgrade installer following JetBrains standard upgrade procedures
- 5. Start the YouTrack service after upgrade completes
- 6. Verify that saved queries and tags are now properly protected by access controls
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57925 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-57925 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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