CVE-2026-49373 in the critical feed json
In JetBrains TeamCity before 2026.1 remote code execution was possible via Perforce connection settings
published 5mo ago modified 3mo ago also EUVD-2026-33381
- cvss
- 7.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 32.7%
- EPSS 32.7% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
In JetBrains TeamCity before 2026.1 remote code execution was possible via Perforce connection settings
Patch / fix
- JetBrains TeamCity 2026.1
Is CVE-2026-49373 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 5mo ago
Exploit prediction
32.69% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- JetBrains TeamCity
Classification
- Weakness
-
- CWE-88 Improper Neutralization of Argument Delimiters in a Command
References
-
jetbrains.com
/privacy-security/issues-fixed/
vendor-advisory
Sources
- CVE List CVE-2026-49373
- NVD CVE-2026-49373
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.