CVE-2026-133263 in YouTrack
Summary
by MITRE • 11/20/2026
In JetBrains YouTrack before 2026.2.19840 missing authorization allowed guests to add issues to sprints
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability identified in versions of JetBrains YouTrack prior to build 2026.2.19840 represents a critical failure in access control mechanisms, specifically classified under CWE-306 as a Missing Authentication for Critical Function. This flaw allows unauthenticated users, commonly referred to as guests or anonymous visitors, to perform state-changing operations that should be restricted to authorized personnel with specific project roles. The core technical issue lies in the application's API endpoints responsible for sprint management not properly validating the session token or authentication credentials of the requesting user before processing requests to modify sprint data structures.
In a typical YouTrack deployment, sprints are used within Agile workflows to organize and track work items over fixed time periods. These operations require elevated privileges because adding issues to an active sprint directly impacts team velocity metrics, resource allocation, and project planning visibility. The vulnerability exploits the lack of server-side authorization checks on these specific endpoints, allowing any user with network access to the YouTrack instance to inject tasks into designated sprints without logging in or possessing valid credentials. This bypasses standard role-based access control policies that would normally restrict such actions to team leads, scrum masters, or project administrators.
The operational impact of this vulnerability is multifaceted and potentially severe depending on the organization's reliance on YouTrack for development lifecycle management. Unauthorized addition of issues can lead to data integrity corruption within sprint boards, causing inaccurate reporting on progress and burndown charts which are critical for Agile ceremonies like sprint planning and retrospectives. Furthermore, malicious actors could use this capability to inject misleading or spam content into active sprints, disrupting team focus and potentially triggering automated workflows or notifications that consume system resources. In environments where YouTrack is integrated with other CI/CD pipelines or project management tools, the injection of unauthorized issues might also trigger downstream processes based on false premises, leading to wasted computational effort and potential misalignment in broader organizational planning efforts.
From a threat intelligence perspective, this vulnerability aligns with ATT&CK technique T1078, Valid Accounts, although in this case it extends to invalid or non-existent accounts due to the complete absence of authentication requirements for certain functions. Attackers could leverage automated scripts to rapidly populate sprints with numerous issues, effectively causing a denial of service through data pollution rather than resource exhaustion. The ease of exploitation means that even low-skilled threat actors can exploit this flaw without needing sophisticated tools or prior reconnaissance beyond identifying the YouTrack instance URL and available sprint identifiers.
Mitigation strategies must prioritize immediate patching to version 2026.2.19840 or later, where JetBrains has implemented strict authentication checks on all sprint modification endpoints. For organizations unable to apply patches immediately due to operational constraints, network-level controls such as firewall rules restricting access to YouTrack API endpoints from untrusted networks can provide temporary relief. Additionally, implementing Web Application Firewall (WAF) signatures that detect and block requests lacking valid session tokens for known sensitive endpoints like sprint updates can serve as an effective compensating control. Regular auditing of user permissions and enforcing strict default-deny policies on guest access to administrative or planning features are also recommended best practices to prevent similar authorization bypasses in the future.