# CVE-2026-106219: JetBrains TeamCity Git submodule URL validation bypass

Source: https://junglewise.ai/threats/cve-2026-106219-in-jetbrains-teamcity-before-2026-2-1-missing-validation-of-git  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-06. Updated: 2026-10-06  
License: CC BY 4.0 with a link back

CVE-2026-106219 · Severity: medium · CVSS 6.5 · Published 2026-10-06

JetBrains TeamCity is a continuous integration server used by development teams to automate builds and deployments. A missing validation of Git submodule URLs allows an attacker to read arbitrary local repositories stored on the TeamCity server, potentially exposing source code and sensitive configuration data.

Technologies: [Jetbrains TeamCity](https://junglewise.ai/threats/technologies/teamcity). Vendors: [Jetbrains](https://junglewise.ai/threats/vendors/jetbrains).

## 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

## References

- [https://www.jetbrains.com/privacy-security/issues-fixed/](https://www.jetbrains.com/privacy-security/issues-fixed/)

## Related threats

- [JetBrains TeamCity stored XSS in classic build log](https://junglewise.ai/threats/cve-2026-111096-in-jetbrains-teamcity-before-2026-2-2026-1-4-2025-11-8-stored)
- [JetBrains TeamCity stored XSS in project overview](https://junglewise.ai/threats/cve-2026-111095-in-jetbrains-teamcity-before-2026-2-2026-1-4-2025-11-8-stored)
- [JetBrains TeamCity remote code execution in build messages protocol](https://junglewise.ai/threats/cve-2026-111094-in-jetbrains-teamcity-before-2026-2-2026-1-4-2025-11-8-remote)
- [JetBrains TeamCity Kotlin DSL sandbox escape RCE](https://junglewise.ai/threats/cve-2026-106218-in-jetbrains-teamcity-before-2026-1-3-2025-11-7-kotlin-dsl)
- [JetBrains TeamCity administrator account takeover via password reset](https://junglewise.ai/threats/cve-2026-100255-in-jetbrains-teamcity-before-2026-2-2026-1-4-2025-11-8)