MEDIUM 4.3

CVE-2026-57925: JetBrains YouTrack Access Control Flaw – Query and Tag Disclosure

JetBrains YouTrack versions before 2026.2.16593 contain an access control flaw that allows authenticated users to read saved queries and tags they should not have permission to access. An attacker with valid login credentials can view sensitive search configurations and organizational metadata without proper authorization checks. This is not a pre-authentication or unauthenticated attack; it requires an existing account on the YouTrack instance.

Source data · NVD / CISA · public domain

CVSS
3.1 · 4.3 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Weaknesses (CWE)
CWE-862
Affected products
1 configuration(s)
Published / Modified
2026-06-26 / 2026-06-27

NVD description (verbatim)

In JetBrains YouTrack before 2026.2.16593 improper access control allowed reading saved queries and tags

1 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

The vulnerability stems from improper access control (CWE-862) in YouTrack's query and tag retrieval mechanisms. The application fails to enforce adequate permission boundaries when returning saved queries and associated tags to authenticated users. This allows a logged-in user to enumerate and read saved queries and tags belonging to other users or organizational contexts beyond their assigned permissions. The issue affects all versions prior to 2026.2.16593, where access control enforcement was strengthened.

Business impact

Organizations using YouTrack for issue tracking and project management may face information disclosure through unauthorized access to saved queries and tags. If these queries contain or reference sensitive projects, restricted team assignments, or confidential search criteria, an internal attacker or compromised user account could gain visibility into workflows and metadata intended for restricted groups. This is particularly concerning in regulated environments where audit trails and segregation of duties matter. The impact is limited to confidentiality; data integrity and system availability are not affected.

Affected systems

JetBrains YouTrack installations running versions prior to 2026.2.16593 are vulnerable. This includes all on-premises and cloud-hosted deployments of YouTrack that have not been updated to the patched version. The vulnerability requires network access to the YouTrack instance and valid user credentials, making it primarily a risk to insider threat scenarios or compromised account scenarios.

Exploitability

Exploitation requires low privileges (a valid user account on the YouTrack instance) and no special user interaction or social engineering. An attacker with credentials can directly request saved queries and tags through normal application operations. The CVSS 3.1 score of 4.3 (MEDIUM severity) reflects the low attack complexity and the requirement for user authentication. Practical risk is elevated in environments with weak password policies, high user turnover, or shared accounts.

Remediation

Organizations must upgrade YouTrack to version 2026.2.16593 or later. Review your current deployment version in YouTrack settings under About and verify the build number. If you are on a managed cloud instance, check with JetBrains for automated update schedules. For on-premises installations, plan an upgrade during maintenance windows, as it may require service restart.

Patch guidance

Upgrade YouTrack to 2026.2.16593 or any subsequent release. Consult the JetBrains YouTrack release notes and upgrade guide to confirm compatibility with your environment and any custom plugins or integrations. Test the upgrade in a non-production environment if possible. After patching, access control enforcement will prevent unauthorized users from reading saved queries and tags belonging to others.

Detection guidance

Monitor YouTrack access logs for unusual query retrieval patterns, particularly users accessing queries they did not create or are not assigned to. Alert on rapid enumeration of saved queries across multiple projects or users. Review audit logs for access to tag metadata by users outside expected roles. Consider implementing network-level monitoring to baseline normal YouTrack API usage patterns, then flag deviations. No specific log signatures are available without vendor guidance, so focus on behavioral anomalies.

Why prioritize this

Although the CVSS score is MEDIUM (4.3) and the vulnerability does not appear on the CISA Known Exploited Vulnerabilities list, it warrants timely patching because access control flaws in collaborative tools create persistent insider risk and compliance complications. The low barrier to exploitation (just needing valid credentials) means any compromised user account or insider threat actor can immediately leverage it. Organizations in regulated industries should prioritize this higher due to audit and data segregation requirements.

Risk score, explained

The CVSS 3.1 score of 4.3 reflects: (1) low attack complexity—no special conditions or tricks required; (2) low attack vector—network-accessible but requires authentication; (3) low privilege requirement—any user can trigger the flaw; (4) low scope impact—only confidentiality is breached, not integrity or availability. The score does not heavily penalize insider threat scenarios, which is why context matters. In environments with strict access controls and low user count, risk may be lower; in high-churn or high-privilege-density deployments, the practical risk is higher than the numerical score suggests.

Frequently asked questions

Do we need to patch immediately, or can we schedule this during normal maintenance?

This can typically be scheduled during regular maintenance windows rather than treated as emergency. However, if your YouTrack instance is widely accessible across teams and you have high user turnover or shared accounts, prioritize it within the next 1–2 release cycles. Review your own access control policies first to assess whether the risk of unauthorized query/tag enumeration is material to your operations.

Will upgrading YouTrack cause downtime or break custom plugins?

Upgrading YouTrack may require a service restart, during which the application will be unavailable. Custom plugins and integrations should be tested for compatibility with 2026.2.16593 before production deployment. Consult the JetBrains migration guide and test in a staging environment to confirm no breaking changes affect your workflows.

What should we do if a user account has been compromised?

Reset the compromised user's password immediately and review their access logs for any unusual query or tag access. If you suspect data has been read, audit which queries and tags they accessed, then notify teams whose sensitive metadata may have been exposed. Consider a temporary suspension of the account while you investigate, and enable multi-factor authentication if not already required.

Is there a workaround if we cannot patch immediately?

No robust technical workaround exists short of patching. As a temporary mitigation, restrict YouTrack access to trusted networks only (via firewall or VPN) and enforce strong password policies and multi-factor authentication to reduce the likelihood of account compromise. However, these do not close the access control flaw itself—patching is the definitive fix.

This analysis is based on the CVE record and vendor advisory as of the publication date. Security advisories and patch availability may be updated by JetBrains; always verify current patch versions and release notes directly from the JetBrains YouTrack website. This vulnerability has not been added to the CISA Known Exploited Vulnerabilities catalog, but absence from KEV does not indicate low risk in your environment. Consult your own risk tolerance, compliance obligations, and asset criticality when determining patch priority. No working exploit code is known to be publicly available, but security researchers and threat actors may develop proof-of-concept tools independently. This summary does not constitute professional security advice; engage your security team or a qualified consultant for decisions on your deployment. Source: NVD (public-domain), retrieved 2026-08-05. Analysis generated by SEC.co (claude-haiku-4-5).