Quick answers
- Is CVE-2026-106219 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106219 being exploited in the wild.
- How severe is CVE-2026-106219?
- Medium severity, with a CVSS score of 6.5, published 6 October 2026.
- Which products and versions are affected?
- Jetbrains TeamCity before 2026.2.1.
- Is there a fix for CVE-2026-106219?
- Yes: fixed in TeamCity 2026.2.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-106219 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-106219?
- Check whether you run Jetbrains TeamCity at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: TeamCity 2026.2.1
Technical details
TeamCity fails to properly validate Git submodule URLs, permitting directory traversal or path manipulation to access repositories outside the intended scope. An authenticated attacker or someone with the ability to submit malicious Git submodule configurations can exploit this to read local repositories on the server. The vulnerability exists in the Git checkout or submodule processing component.
Affected products
- JetBrains TeamCity before 2026.2.1
Timeline
- 2026-10-06: disclosed