In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via Mercurial repository contents
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2026-132909 is a critical remote code execution vulnerability affecting JetBrains TeamCity versions prior to 2026.2, 2026.1.4, and 2025.11.8. The vulnerability stems from improper handling of Mercurial repository contents, allowing attackers to execute arbitrary code on systems running vulnerable TeamCity instances. This matters significantly because TeamCity is widely deployed in enterprise CI/CD pipelines as a central orchestration point—compromising it grants attackers access to build systems, source code, artifacts, and credentials stored within the pipeline. Organizations using Mercurial as their version control system are directly at risk, particularly those integrating TeamCity with untrusted or external repositories.
While this CVE lacks direct MITRE ATT&CK technique mappings, Casky's Claude-powered analysis would detect attack patterns associated with supply chain compromise and code execution. Practitioners using Casky would observe detection patterns correlating to Execution techniques (T1203 - Exploitation for Client Execution) through malicious repository content triggering code execution, alongside Supply Chain Compromise (T1195.001) where poisoned Mercurial repositories serve as attack vectors. The underlying CWE-88 (Argument Injection) suggests attackers manipulate repository parameters or metadata to inject malicious commands. With zero matching Casky skills currently indexed for this specific vulnerability, security teams should prioritize immediate patching and monitor for suspicious Mercurial repository interactions, authentication anomalies in build systems, and unexpected code execution patterns emanating from TeamCity processes during their build operations.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-132909. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation