CVE-2026-57922: YouTrack MCP Project Settings Disclosure (Low Severity)

Technical summary

CVE-2026-57922 is an authorization bypass vulnerability in YouTrack's MCP implementation that permits authenticated users to access project configuration details they should not be able to view. The flaw stems from insufficient access control checks (CWE-862) when MCP queries project settings, allowing credential holders to enumerate or retrieve sensitive project metadata. The attack vector is network-based and requires prior authentication, limiting the threat surface to users with legitimate system access.

Business impact

Project settings often contain workflow configurations, field definitions, custom integrations, and process documentation that may be considered proprietary or operationally sensitive. Unauthorized disclosure could inform competitors or malicious insiders about internal practices, though the vulnerability does not enable modification or deletion of data. For organizations treating YouTrack as a critical issue-tracking system, this represents a confidentiality risk rather than a data integrity or availability threat.

Affected systems

JetBrains YouTrack deployments before version 2026.2.16593 are affected. This includes on-premises installations and cloud-hosted instances running vulnerable builds. Organizations using YouTrack's MCP feature—which connects to external tools and models for enhanced querying or automation—face higher exposure than those with MCP disabled or not configured.

Exploitability

Exploitation requires valid YouTrack credentials, making opportunistic attacks unlikely unless an attacker already has user-level access or compromises a legitimate account. The attack complexity is marked as high in the CVSS vector, suggesting specific conditions or configurations must be present. No known public exploits or active exploitation campaigns have been disclosed, and the vulnerability is not listed on the CISA Known Exploited Vulnerabilities catalog.

Remediation

Upgrade YouTrack to version 2026.2.16593 or later to remediate the authorization bypass. For organizations unable to patch immediately, consider restricting MCP access to trusted, internal-only integrations and review IAM policies to limit YouTrack user accounts to those with genuine need. Disabling MCP entirely eliminates the attack surface if the feature is not actively used.

Patch guidance

JetBrains has released YouTrack 2026.2.16593 and subsequent releases to address this vulnerability. Customers should consult the official JetBrains YouTrack release notes and security advisories to confirm the exact fix version for their deployment model (cloud vs. on-premises). Apply updates during a scheduled maintenance window; given the low severity and lack of known active exploitation, standard change management procedures are appropriate.

Detection guidance

Monitor YouTrack audit logs for unusual MCP-initiated queries, particularly those accessing project settings by non-admin accounts or service principals. Look for patterns of repeated project configuration requests via MCP that deviate from normal workflow. Network monitoring can identify unexpected outbound MCP traffic if the integration is not typically used. Conduct a post-patch audit to verify that unauthorized project setting disclosures have not occurred in your instance.

Why prioritize this

This vulnerability scores 3.1 (LOW) due to the requirement for prior authentication, high attack complexity, and limited impact (confidentiality only). It does not qualify for emergency patching but warrants inclusion in the next standard release cycle. Organizations should prioritize patching only if they actively use MCP and handle highly sensitive project configurations; others may defer to routine maintenance windows.

Risk score, explained

The CVSS 3.1 score of 3.1 reflects: Network accessibility (AV:N), high attack complexity (AC:H), and a requirement for low privileges and authentication (PR:L, UI:N). The impact is restricted to confidentiality (C:L) with no integrity or availability impact (I:N, A:N), and no scope escalation. The high complexity requirement and authenticated-only prerequisite constrain the overall risk.

Frequently asked questions