Last updated
Powerful continuous integration for DevOps-centric teams
$ winget install --id JetBrains.TeamCity --exact --version 2026.1.1Run in Command Prompt, PowerShell, or Windows Terminal. Prompts for any agreements.
JetBrains TeamCity uses EXE (NSIS). The silent install switches are /S.
TeamCity-2026.1.1.exe /S
See the full silent install reference for JetBrains TeamCity →
For Intune admins
Automated application patching for Microsoft Intune. Pckgr keeps a curated library of 1,000+ apps continuously up-to-date in your tenant via Microsoft Graph - no manual repackaging, no chasing vendor sites.
Start free 30-day trialNo credit card required.
The powerful Continuous Integration and Deployment tool for Developers and DevOps Engineers.
| Architecture | Type | Scope | Install | Download |
|---|---|---|---|---|
| x64 | EXE NSIS | machine | Direct |
Copy a command tailored to that specific architecture, type, and scope - useful when winget would otherwise pick a different default.
25 known CVEs via NVD
In JetBrains TeamCity before 2026.1 stored XSS on the SAML login page was possible
In JetBrains TeamCity before 2026.1 open redirect in the SAML plugin was possible
In JetBrains TeamCity before 2026.1 credentials could be exposed in thread names
In JetBrains TeamCity before 2026.1 credentials parameters were exposed via parameter autocompletion
In JetBrains TeamCity before 2025.11.2 exposure of sensitive data via default agent parameters
In JetBrains TeamCity before 2026.1 insufficient username validation in the SAML plugin
In JetBrains TeamCity before 2026.1, 2025.11.5 reflected XSS was possible on the repository download page
In JetBrains TeamCity before 2026.1 improper permission checks exposed build configuration parameters
See a CVE that affects your fleet? Push the patched version to Intune in one click with Pckgr - automated patching is the only way to keep up.
More from JetBrains s.r.o. or browse cd, ci, develop.