Authenticated code execution via Git VCS roots
Published Jul 23, 2026 · Updated Jul 23, 2026
Code injection in JetBrains TeamCity before 2026.1.2 and 2025.11.6 allows remote authenticated users to execute code through Git VCS roots. JetBrains identifies Git VCS root processing as the affected locus but has not published the specific input, code path, or unsafe operation. Exploitation requires high-privileged TeamCity access and can compromise data, server state, and resources reachable with the executing process's authority.
Summary
What happened
Code injection in JetBrains TeamCity before 2026.1.2 and 2025.11.6 allows remote authenticated users to execute code through Git VCS roots. JetBrains identifies Git VCS root processing as the affected locus but has not published the specific input, code path, or unsafe operation. Exploitation requires high-privileged TeamCity access and can compromise data, server state, and resources reachable with the executing process's authority.
The record
- CVE
- CVE-2026-65907
- Published
- Jul 23, 2026
- Updated
- Jul 23, 2026
- Vendor
- JetBrains
- Product
- TeamCity On-Premises
- Classifications
- CWE-94
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 23, 2026CVE publishedPublication date reported by the CVE source.
- Jul 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2026.1.2, 2025.11.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo