| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| FlowIntel contains an authorization flaw in its duplicate alert ingestion logic. When a duplicate alert is received and its content is updated, the ownership and visibility scope fields (owner user and owner organization) were not refreshed to reflect the connector's current scope. As a result, an alert that was originally created under a broader visibility scope retained that broader scope even after the connector's scope was narrowed or changed.
This means that users or organizations that should no longer have visibility into a given alert could continue to access it, because the stale ownership fields were never updated during the duplicate-update path. The issue affected all duplicate updates, including those involving alerts in terminal review states and those recovered from uniqueness conflicts.
Security impact:
- Unauthorized disclosure of security alert content to users or organizations outside the intended visibility scope.
- Stale access persists indefinitely until the alert is independently re-scoped or deleted.
Affected version: <4.1.0. |
| In JetBrains TeamCity before 2026.2 mute and unmute operations via XML-RPC could be attributed to other users |
| In JetBrains TeamCity before 2026.2 stored XSS on the build step settings page was possible |
| In JetBrains TeamCity before 2026.2 the REST API exposed details of users not visible in the UI |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the notification rules editor was possible |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the agent info popup was possible |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Slack connection test page was possible |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in Change Log revision tooltips was possible |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the SSH Keys page was possible |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 the Cloud Profiles page disclosed cloud profiles of projects the user could not access |
| In JetBrains TeamCity before 2026.2 server certificates were not verified in the SVN integration |
| In JetBrains TeamCity before 2026.2 password parameters containing a caret were not masked in build logs on Windows |
| In JetBrains TeamCity before 2026.2 project administrators could read OAuth connection secrets of ancestor projects |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the project Report Tab dialog was possible |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Report Tabs settings page was possible |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the build Report Tab dialog was possible |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Versioned Settings page was possible |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Schedule Trigger branch filter settings was possible |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the checkout rules editor was possible |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in agent requirements was possible |