In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS on the Projects Import page was possible
Search vulnerabilities
In JetBrains TeamCity before 2026.2.2, 2026.1.6 hTML injection in pipeline notification emails was possible via commit messages
In JetBrains TeamCity before 2026.2.2 the current request details debug endpoint exposed authentication headers and session cookies
In JetBrains TeamCity before 2026.2.2, 2026.1.6 hTML injection in pipeline notification emails was possible via user and job names
In JetBrains Rider before 2026.3 code execution was possible via MSBuild configuration files in parent directories
In JetBrains ReSharper before 2026.3 the What's New feature did not verify server certificates
In JetBrains Junie GitHub Action before 1.10.0 code execution was possible via path traversal in feedback session markers
In JetBrains Junie GitHub Action before 1.10.0 command injection was possible via the action version input
In JetBrains Junie CLI before 26.11.1 files outside the project could be overwritten via shell output redirection
In JetBrains Datalore before 2026.4.1 improper authorization allowed notebook viewers to read attached environment variable values
CVE-2026-22062 Information Exposure Vulnerability in StorageGRID (formerly StorageGRID Webscale)
StorageGRID (formerly StorageGRID Webscale) versions 12.1.0 and higher are susceptible to an information exposure vulnerability which allows a remote unauthenticated attacker to acquire low-sensitivity credentials via a Man-in-the-middle attack when certain non-default features are enabled.
Local Intent Abuse Causing Unauthorized Voice Commands in Vivo Assistant
An improper export control defect in ChatEventDispatchActivity (com.vivo.agent.business.chatmode.activity.ChatEventDispatchActivity) of Vivo Assistant allows a local malicious application to execute voice commands without user interaction via a crafted Intent, which may lead to unauthorized phone calls, SMS sending, access to private data such as location and calendar entries, and modification of system settings
Certificate Chain Verification Failure in WhatsApp Enables Root of Trust Bypass
Improper following of a certificate’s chain of trust in the remote-attestation verifier used to establish trust with Meta AI's confidential computing backend in WhatsApp for iOS before 2.26.24.72, WhatsApp Business for iOS and WhatsApp for Mac Desktop before v2.26.23.72, WhatsApp for Android before v2.26.23.74, and WhatsApp Business for Android before v2.26.23.70 could have allowed someone positioned within Meta infrastructure to bypass the hardware root of trust by presenting clients with a VCEK certificate signed by a key other than the hardware manufacturer’s. Any such VCEK Cert would first have to be published to the third-party binary transparency ledger used by WhatsApp Private Processing. The ledger shows that every published VCEK certificate chains to the hardware root of trust, confirming no exploitation.
In JetBrains YouTrack before 2026.2.19840 app widgets could perform API requests on behalf of viewing users without their consent
In JetBrains YouTrack before 2026.2.19840 privilege escalation from project administrator to system administrator was possible via group merging
In JetBrains YouTrack before 2026.2.19840 an HTML injection in email notifications was possible via issue descriptions
In JetBrains YouTrack before 2026.2.19840 private issue summaries and descriptions could be read via agile board queries for archived projects
In JetBrains YouTrack before 2026.2.19840 the attachment upload size limit could be bypassed via the REST API
In JetBrains YouTrack before 2026.2.19766 helpdesk email attachments were sent to CC recipients without a visibility check
In JetBrains YouTrack before 2026.2.19840 project members could detach inline comment threads of other users on articles