In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on build and queue pages was possible
Export limit exceeded: 18782 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search vulnerabilities
In JetBrains TeamCity before 2026.2 two-factor authentication bypass was possible via access token management
In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in the unified diff page syntax highlighting was possible
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in SSH key management was possible
In JetBrains TeamCity before 2026.2, 2026.1.4 improper authorization allowed users with the Run build permission to delete Perforce workspaces
In JetBrains TeamCity before 2026.2 stored XSS in the duplicate remote parameter health report was possible
In JetBrains TeamCity before 2026.2, 2026.1.4 the Perforce Administrator Access password could be written to the server log
In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in Perforce job details was possible
In JetBrains TeamCity before 2026.2, 2026.1.4 reflected XSS on the notification rules page was possible
In JetBrains TeamCity before 2026.2, 2026.1.4 reflected XSS in build problem details was possible
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the build feature parameters page was possible
In JetBrains TeamCity before 2026.2 privilege escalation of project-scoped access tokens via concurrent project deletion was possible
In JetBrains TeamCity before 2026.2, 2026.1.4 authentication bypass via polling agent name rebinding was possible
In JetBrains TeamCity before 2026.2, 2026.1.4 arbitrary file write via read-write file channels in the Kotlin DSL sandbox was possible
In JetBrains TeamCity before 2026.2 improper authorization allowed project-limited access tokens to act with full permissions via XML-RPC
In JetBrains TeamCity before 2026.2, 2026.1.4 missing authorization allowed users to remove all build configuration assignments from an agent
Authentication Bypass through the RapidDiag REST API in Splunk Enterprise
In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could run arbitrary Search Processing Language (SPL) searches through RapidDiag task collection as an authenticated user. With this access, the user could read or modify data and configuration available to that authenticated user. The vulnerability is possible because Splunk Enterprise accepts an empty shared secret when it authenticates RapidDiag task-collection requests. For more information see Using RapidDiag (https://help.splunk.com/en/splunk-enterprise/administer/troubleshoot/9.3/contact-splunk-support/using-rapiddiag) in the Splunk documentation.
Authentication Bypass through the Cluster Configuration REST API in Splunk Enterprise
In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could use an empty clustering shared secret to read and modify clustering configuration through the cluster configuration Representational State Transfer (REST) API endpoint on a standalone instance. This could expose clustering configuration, persist attacker-controlled clustering settings, and disrupt clustering operations. The vulnerability is possible because Splunk Enterprise accepts the empty clustering shared secret as a shared-authentication candidate on a standalone instance when clustering is turned off.
Improper Access Control through the REST API in Splunk Enterprise
In Splunk Enterprise versions below 10.4.4, 10.2.9, 10.0.12, and 9.4.16, a user who does not hold the "admin" or "power" Splunk roles could use the search jobs Representational State Transfer (REST) API to access indexed events that the srchFilter setting for the role should hide. The same user could also run internal Search Processing Language (SPL) commands and bypass SPL safeguards for risky commands within indexes that the role can search. The vulnerability is possible because Splunk Enterprise does not correctly escape required field values before it includes them in an internally generated search. For more information, see Search endpoint descriptions (https://help.splunk.com/en/splunk-enterprise/rest-api-reference/9.4/search-endpoints/search-endpoint-descriptions), authorize.conf (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.4/configuration-file-reference/10.4.5-configuration-file-reference/authorize.conf), and SPL safeguards for risky commands (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/best-practices-for-splunk-platform-security/spl-safeguards-for-risky-commands).
Improper Authorization through the REST API in Splunk Enterprise
In Splunk Enterprise versions below 9.4.17, 10.0.12, 10.2.9, and 10.4.5, a user who does not hold the "admin" or "power" Splunk roles can configure a metric alert through the Representational State Transfer (REST) API that runs a search with elevated privileges. The vulnerability lets the user access or modify data and disrupt the Splunk Enterprise instance. The vulnerability occurs because Splunk Enterprise does not enforce the required role-based authorization when it processes metric alert configuration through the REST API. Splunk Enterprise schedules the resulting search with elevated authorization and runs attacker-controlled search processing with that authorization. For more information see About configuring role-based user access (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/manage-splunk-platform-users-and-roles/about-configuring-role-based-user-access) in the Splunk documentation.