Exposição de TeamCity

CI
166
score de exposição
1
sites usam
4
em exploração
11
críticos
Análise Vexday

TeamCity acumula 176 CVEs catalogadas, com 3 confirmadas em exploração ativa no catálogo KEV da CISA — uma taxa 3,8 vezes acima da média geral do catálogo, o que indica risco operacional concreto e não apenas teórico. O pior caso ativo no momento é CVE-2024-27199, com EPSS de 0,9999, sinalizando probabilidade de exploração próxima da certeza estatística e exigindo atenção imediata de equipes de resposta. O tipo de falha mais frequente é CWE-79 (Cross-Site Scripting), mas a presença de 4 CVEs críticas e 12 vulnerabilidades surgidas nos últimos 90 dias aponta para uma superfície de ataque ainda em expansão. Ambientes que executam TeamCity devem priorizar a aplicação de patches recentes e monitorar ativamente indicadores de comprometimento associados às vulnerabilidades em exploração confirmada.

CVEs

393 resultados
CVE-2026-132239HIGHIn JetBrains TeamCity before 2026.1.3, 2025.11.7 missing authorization in the Kubernetes integration allowed project viewers to use stored cEPSS 0.3%CVE-2026-133094HIGHIn JetBrains TeamCity before 2026.2.2 missing authorization allowed project developers to read arbitrary HashiCorp Vault secretsEPSS 0.3%CVE-2025-68164LOWIn JetBrains TeamCity before 2025.11 port enumeration was possible via the Perforce connection testEPSS 0.3%CVE-2026-133049MEDIUMIn JetBrains TeamCity before 2026.2.1 stored XSS in the Pull Requests health report for VCS roots was possibleEPSS 0.3%CVE-2026-133038MEDIUMIn JetBrains TeamCity before 2026.2.1 stored XSS in the Maven Build Info project header was possibleEPSS 0.3%CVE-2026-133103MEDIUMIn JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS in the enforced settings restriction tooltip was possibleEPSS 0.3%CVE-2026-133042MEDIUMIn JetBrains TeamCity before 2026.2.1 stored XSS in the Amazon EC2 cloud profile editor was possibleEPSS 0.3%CVE-2026-133039MEDIUMIn JetBrains TeamCity before 2026.2.1 stored XSS in the Pull Requests health report for Space connections was possibleEPSS 0.3%CVE-2026-133045MEDIUMIn JetBrains TeamCity before 2026.2.1 stored XSS in VMware vSphere cloud profile settings was possibleEPSS 0.3%CVE-2026-133046MEDIUMIn JetBrains TeamCity before 2026.2.1 stored XSS in recipe export errors was possibleEPSS 0.3%CVE-2026-49379MEDIUMIn JetBrains TeamCity before 2026.1 credentials could be exposed in thread namesEPSS 0.3%CVE-2024-36371MEDIUMIn JetBrains TeamCity before 2023.05.6, 2023.11.5 stored XSS in Commit status publisher was possibleEPSS 0.3%CVE-2025-54533MEDIUMIn JetBrains TeamCity before 2025.07 improper access control allowed disclosure of build settings via VCS configurationEPSS 0.3%CVE-2025-54532MEDIUMIn JetBrains TeamCity before 2025.07 improper access control allowed disclosure of build settings via snapshot dependenciesEPSS 0.3%CVE-2026-133091HIGHIn JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS on the Users page was possibleEPSS 0.3%CVE-2026-49374HIGHIn JetBrains TeamCity before 2026.1 improper permission checks exposed build configuration parametersEPSS 0.3%CVE-2026-132247MEDIUMIn JetBrains TeamCity before 2026.1.3, 2025.11.7 improper authorization allowed viewing build process details via agent stacktracesEPSS 0.3%CVE-2026-133057LOWIn JetBrains TeamCity before 2026.2.1, 2026.1.5 the TFS helper server was exposed on all network interfacesEPSS 0.3%CVE-2026-133083HIGHIn JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS in Server Health reports was possibleEPSS 0.2%CVE-2026-133102MEDIUMIn JetBrains TeamCity before 2026.2.2, 2026.1.6 out-of-band data exfiltration via DNS resolution was possible in the Kotlin DSL sandboxEPSS 0.2%