Vulnerability database · updated every 15 minutes

New vulnerabilities in the software websites run.

CVEs and security advisories for WordPress, its plugins and themes, npm, PyPI and the servers behind websites, merged from NVD, the CVE Program, GitHub, OSV.dev and WPVulnerability, with CISA's list of the ones attackers exploit.

Free · right away or once a day · unsubscribe in one click
Tracked
55,399
Published in 7 days
1,895
Critical in 30 days
489
Actively exploited
542
Clear filters

Results for “TeamCity”

486 vulnerabilities
  1. Critical 9.9

    CVE-2026-132233 · TeamCity

    In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via build attribute injection

    Published 18 Nov 2026 · Fixed in 2025.11.7, 2026.1.3 · CVE Program
  2. Critical 9.9

    CVE-2026-132232 · TeamCity

    In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via argument injection in Perforce settings

    Published 18 Nov 2026 · Fixed in 2025.11.7, 2026.1.3 · CVE Program
  3. Critical 9.9

    CVE-2026-132231 · TeamCity

    In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via best-fit character mapping in Perforce settings

    Published 18 Nov 2026 · Fixed in 2025.11.7, 2026.1.3 · CVE Program
  4. Medium 5.4

    CVE-2026-111096 · TeamCity

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the classic build log was possible

    Published 15 Oct 2026 · Fixed in 2026.2, 2026.1.4, 2025.11.8, 2025.11.8, 2026.1.4 · NVD, CVE Program
  5. Medium 5.4

    CVE-2026-111095 · TeamCity

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the classic project overview was possible

    Published 15 Oct 2026 · Fixed in 2026.2, 2026.1.4, 2025.11.8, 2025.11.8, 2026.1.4 · NVD, CVE Program
  6. Critical 9.8

    CVE-2026-111094 · TeamCity

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution via a whitelist bypass in the build messages protocol was possible

    Published 15 Oct 2026 · Fixed in 2026.2, 2026.1.4, 2025.11.8, 2025.11.8, 2026.1.4 · NVD, CVE Program
  7. High 7.5

    CVE-2026-106219 · TeamCity

    In JetBrains TeamCity before 2026.2.1 missing validation of Git submodule URLs allowed reading local repositories on the server

    Published 6 Oct 2026 · Fixed in 2026.2.1 · NVD, CVE Program
  8. Critical 10.0

    CVE-2026-106218 · TeamCity

    In JetBrains TeamCity before 2026.1.3 2025.11.7 kotlin DSL sandbox escape leading to RCE on the server was possible

    Published 6 Oct 2026 · Fixed in 2026.1.3 2025.11.7, 2025.11.7, 2026.1.3 · NVD, CVE Program
  9. Critical 9.8

    CVE-2026-100255 · TeamCity

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 administrator account takeover was possible via password reset

    Published 30 Sept 2026 · Fixed in 2025.11.8, 2026.1.4 · NVD
  10. High 8.8

    CVE-2026-100254 · TeamCity

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 authenticated users could execute commands on Windows servers via CRLF injection in Pipeline Git connection settings

    Published 30 Sept 2026 · Fixed in 2025.11.8, 2026.1.4 · NVD
  11. High 8.8

    CVE-2026-100253 · TeamCity

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 sandbox escape leading to code execution was possible via the versioned settings Kotlin DSL

    Published 30 Sept 2026 · Fixed in 2025.11.8, 2026.1.4 · NVD
  12. Critical 9.8Actively exploited

    CVE-2026-63077 · TeamCity

    In JetBrains TeamCity before 2026.1.3, 2025.11.7 unauthenticated remote code execution was possible via the agent polling protocol

    Published 27 Jul 2026 · Fixed in 2025.11.7, 2026.1.3 · NVD
  13. Critical 10.0

    CVE-2026-65906 · TeamCity

    In JetBrains TeamCity before 2026.1.2, 2025.11.6 сode execution via Kotlin DSL sandbox escape was possible

    Published 23 Jul 2026 · Fixed in 2025.11.6, 2026.1.2 · NVD
  14. High 8.1

    CVE-2026-59796 · TeamCity

    In JetBrains TeamCity before 2026.1.2 pipeline modification was possible due to improper permission checks

    Published 10 Jul 2026 · Fixed in 2026.1.2 · NVD
  15. Medium 6.1

    CVE-2026-59795 · TeamCity

    In JetBrains TeamCity before 2026.1.2 stored XSS via unauthenticated agent registration was possible

    Published 10 Jul 2026 · Fixed in 2026.1.2 · NVD
  16. Medium 5.4

    CVE-2026-59794 · TeamCity

    In JetBrains TeamCity before 2026.1.2 stored XSS on the cloud profile page was possible via agent-reported data

    Published 10 Jul 2026 · Fixed in 2026.1.2 · NVD
  17. High 8.8

    CVE-2026-59793 · TeamCity

    In JetBrains TeamCity before 2026.1.2 arbitrary file access was possible via the Perforce VCS integration

    Published 10 Jul 2026 · Fixed in 2026.1.2 · NVD
  18. Medium 4.8

    CVE-2026-49381 · TeamCity

    In JetBrains TeamCity before 2026.1 stored XSS on the SAML login page was possible

    Published 29 May 2026 · Fixed in 2026.1 · NVD
  19. Medium 6.1

    CVE-2026-49380 · TeamCity

    In JetBrains TeamCity before 2026.1 open redirect in the SAML plugin was possible

    Published 29 May 2026 · Fixed in 2026.1 · NVD
  20. Medium 6.5

    CVE-2026-49379 · TeamCity

    In JetBrains TeamCity before 2026.1 credentials could be exposed in thread names

    Published 29 May 2026 · Fixed in 2026.1 · NVD
  21. Medium 4.3

    CVE-2026-49378 · TeamCity

    In JetBrains TeamCity before 2026.1 credentials parameters were exposed via parameter autocompletion

    Published 29 May 2026 · Fixed in 2026.1 · NVD
  22. Medium 4.3

    CVE-2026-49377 · TeamCity

    In JetBrains TeamCity before 2025.11.2 exposure of sensitive data via default agent parameters

    Published 29 May 2026 · Fixed in 2025.11.2 · NVD
  23. Medium 6.5

    CVE-2026-49376 · TeamCity

    In JetBrains TeamCity before 2026.1 insufficient username validation in the SAML plugin

    Published 29 May 2026 · Fixed in 2026.1 · NVD
  24. Medium 6.1

    CVE-2026-49375 · TeamCity

    In JetBrains TeamCity before 2026.1, 2025.11.5 reflected XSS was possible on the repository download page

    Published 29 May 2026 · Fixed in 2025.11.5 · NVD
  25. High 7.6

    CVE-2026-49374 · TeamCity

    In JetBrains TeamCity before 2026.1 improper permission checks exposed build configuration parameters

    Published 29 May 2026 · Fixed in 2026.1 · NVD
  26. High 8.8

    CVE-2026-49373 · TeamCity

    In JetBrains TeamCity before 2026.1 remote code execution was possible via Perforce connection settings

    Published 29 May 2026 · Fixed in 2026.1 · NVD
  27. High 7.5

    CVE-2026-49372 · TeamCity

    In JetBrains TeamCity before 2026.1, 2025.11.5 unauthenticated SSRF via build status was possible

    Published 29 May 2026 · Fixed in 2025.11.5 · NVD
  28. High 8.2

    CVE-2026-49371 · TeamCity

    In JetBrains TeamCity before 2026.1.1 reflected XSS in the keyword filter was possible

    Published 29 May 2026 · Fixed in 2026.1.1 · NVD
  29. High 7.5

    CVE-2026-44413 · TeamCity

    In JetBrains TeamCity before 2026.1 2025.11.5 authenticated users could expose server API to unauthorised access

    Published 11 May 2026 · Fixed in 2025.11.5 · NVD
  30. Low 2.3

    CVE-2026-28196 · TeamCity

    In JetBrains TeamCity before 2025.11.3 disabling versioned settings left a credentials config on disk

    Published 25 Feb 2026 · Fixed in 2025.11.3 · NVD
  31. Medium 4.3

    CVE-2026-28195 · TeamCity

    In JetBrains TeamCity before 2025.11.3 missing authorization allowed project developers to add parameters to build configurations

    Published 25 Feb 2026 · Fixed in 2025.11.3 · NVD
  32. Medium 6.1

    CVE-2026-28194 · TeamCity

    In JetBrains TeamCity before 2025.11.3 open redirect was possible in the React project creation flow

    Published 25 Feb 2026 · Fixed in 2025.11.3 · NVD
  33. Medium 6.1

    CVE-2025-68268 · TeamCity

    In JetBrains TeamCity before 2025.11.1 reflected XSS was possible on the storage settings page

    Published 16 Dec 2025 · Fixed in 2025.11.1 · NVD
  34. Medium 6.5

    CVE-2025-68267 · TeamCity

    In JetBrains TeamCity before 2025.11.1 excessive privileges were possible due to storing GitHub personal access token instead of an installation token

    Published 16 Dec 2025 · Fixed in 2025.11.1 · NVD
  35. Medium 6.1

    CVE-2025-68166 · TeamCity

    In JetBrains TeamCity before 2025.11 a DOM-based XSS was possible on the OAuth connections tab

    Published 16 Dec 2025 · Fixed in 2025.11 · NVD
  36. Medium 6.1

    CVE-2025-68165 · TeamCity

    In JetBrains TeamCity before 2025.11 reflected XSS was possible on VCS Root setup

    Published 16 Dec 2025 · Fixed in 2025.11 · NVD
  37. Low 2.7

    CVE-2025-68164 · TeamCity

    In JetBrains TeamCity before 2025.11 port enumeration was possible via the Perforce connection test

    Published 16 Dec 2025 · Fixed in 2025.11 · NVD
  38. Medium 4.8

    CVE-2025-68163 · TeamCity

    In JetBrains TeamCity before 2025.11 stored XSS was possible on agentpushInstall page

    Published 16 Dec 2025 · Fixed in 2025.11 · NVD
  39. Low 2.7

    CVE-2025-68162 · TeamCity

    In JetBrains TeamCity before 2025.11 maven embedder allowed loading extensions via project configuration

    Published 16 Dec 2025 · Fixed in 2025.11 · NVD
  40. High 7.5

    CVE-2025-67742 · TeamCity

    In JetBrains TeamCity before 2025.11 path traversal was possible via file upload

    Published 11 Dec 2025 · Fixed in 2025.11 · NVD
  41. Medium 5.4

    CVE-2025-67741 · TeamCity

    In JetBrains TeamCity before 2025.11 stored XSS was possible via session attribute

    Published 11 Dec 2025 · Fixed in 2025.11 · NVD
  42. Medium 5.3

    CVE-2025-67740 · TeamCity

    In JetBrains TeamCity before 2025.11 improper access control could expose GitHub App token's metadata

    Published 11 Dec 2025 · Fixed in 2025.11 · NVD
  43. Low 3.1

    CVE-2025-67739 · TeamCity

    In JetBrains TeamCity before 2025.11.2 improper repository URL validation could lead to local paths disclosure

    Published 11 Dec 2025 · Fixed in 2025.11.2 · NVD
  44. High 7.7

    CVE-2025-59457 · TeamCity

    In JetBrains TeamCity before 2025.07.2 missing Git URL validation allowed credential leakage on Windows

    Published 17 Sept 2025 · Fixed in 2025.07.2 · NVD
  45. Medium 5.5

    CVE-2025-59456 · TeamCity

    In JetBrains TeamCity before 2025.07.2 path traversal was possible during project archive upload

    Published 17 Sept 2025 · Fixed in 2025.07.2 · NVD
  46. Medium 4.2

    CVE-2025-59455 · TeamCity

    In JetBrains TeamCity before 2025.07.2 project isolation bypass was possible due to race condition

    Published 17 Sept 2025 · Fixed in 2025.07.2 · NVD
  47. Medium 6.5

    CVE-2025-57734 · TeamCity

    In JetBrains TeamCity before 2025.07.1 aWS credentials were exposed in Docker script files

    Published 20 Aug 2025 · Fixed in 2025.07.1 · NVD
  48. Low 3.8

    CVE-2025-57733 · TeamCity

    In JetBrains TeamCity before 2025.07.1 sMTP injection was possible allowing modification of email content

    Published 20 Aug 2025 · Fixed in 2025.07.1 · NVD
  49. Medium 6.3

    CVE-2025-57732 · TeamCity

    In JetBrains TeamCity before 2025.07.1 privilege escalation was possible due to incorrect directory ownership

    Published 20 Aug 2025 · Fixed in 2025.07.1 · NVD
  50. Medium 5.5

    CVE-2025-54538 · TeamCity

    In JetBrains TeamCity before 2025.07 password exposure was possible via command line in the "hg pull" command

    Published 28 Jul 2025 · Fixed in 2025.07 · NVD

Where it comes from

The list holds every advisory UpHeron reads for the software it watches: WordPress and every plugin and theme its plugin reports, the packages in monitored repositories and manifests, and the servers and frameworks found on monitored websites. One vulnerability from several sources is one entry, under its CVE.

  • NVD, the US National Vulnerability Database. This product uses the NVD API but is not endorsed or certified by the NVD.
  • New and changed records of the CVE Program, read every 15 minutes, so a rating or fix added after a CVE is published reaches the list, and its alerts, within the hour. CVE content © 1999–2026 The MITRE Corporation, used under the CVE terms of use; CVE® is a registered trademark of The MITRE Corporation.
  • OSV.dev, with the GitHub Advisory Database (CC BY 4.0).
  • WPVulnerability (CC0) for WordPress plugins and themes, and WordPress's own security advisories.
  • Node.js's own security release posts, read every 15 minutes, which name its vulnerabilities the day they are fixed, days before their CVE records.
  • The security advisories projects publish on GitHub, and the CVEs libraries such as Brotli name in their release notes, which also count for the runtimes that bundle them.
  • CISA's Known Exploited Vulnerabilities catalog.

Each day's new ones, grouped, and every critical one as soon as we find it: on the blog.

Run WordPress? The UpHeron plugin alerts you the day one of these affects your own site.