Security readout for executives and security teams
Plain-English summary
JetBrains TeamCity before 2026.1 had a flaw where Perforce connection settings could allow remote code execution. This matters because TeamCity often controls build pipelines and secrets. The CVSS score is high, but the vector indicates an authenticated low-privileged user is required.
Executive priority
Treat this as a near-term remediation item for any TeamCity deployment, especially CI systems tied to production code or secrets. Prioritize upgrade and permission review.
Technical view
CVE-2026-49373 is a TeamCity remote code execution issue tied to Perforce connection settings. The CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N, and CWE-88 is listed, indicating argument delimiter or command argument handling risk.
Likely exposure
Organizations running JetBrains TeamCity versions before 2026.1 are the stated exposure. Risk is higher where low-privileged users can create or modify Perforce connection settings or VCS configuration.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not marked KEV. The score indicates exploitation is network-reachable, low complexity, requires low privileges, and needs no user interaction.
Researcher notes
Public detail is limited in the supplied bundle. The vulnerability is tied specifically to Perforce connection settings; do not generalize to all TeamCity integrations without vendor confirmation.
Mitigation direction
Upgrade JetBrains TeamCity to 2026.1 or later.
Review JetBrains fixed-issues guidance for any additional vendor instructions.
Restrict who can create or edit Perforce connection settings.
Review TeamCity users and project permissions for unnecessary access.
Monitor TeamCity logs for unexpected Perforce setting changes.
Validation and detection
Inventory all TeamCity servers and record their versions.
Confirm each instance is running 2026.1 or later.
Identify projects using Perforce connections.
Review who can modify VCS roots or connection settings.
Check recent configuration changes around Perforce settings.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-88: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-88 · source CWE mapping
Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')
Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.