Skip to main content
VulnerabilityPublished

CVE-2026-132902: JetBrains TeamCity · Insertion of Sensitive Information Into Sent Data

Affects JetBrains TeamCitySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.7 High : upgrade to 2026.1.4 or 2025.11.8 soon.

Data as of 19 Nov 2026, 11:19 UTC

CVSS 3.1 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (JetBrains)CVSS 3.17.7
Patch
Available – fixed in 2026.1.4, 2025.11.8
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade JetBrains TeamCity to 2026.1.4 or 2025.11.8.

Affected software

ProductAffectedFixed in
JetBrainsTeamCityAffected
  • >=2026.1 <2026.1.4
Fixed in
  • 2026.1.4
JetBrainsTeamCityAffected
  • <2025.11.8
Fixed in
  • 2025.11.8

AI-suggested

Apply the official JetBrains TeamCity updates to versions 2026.1.4 or later, or 2025.11.8 or later, which contain the fix for this vulnerability. Since this is a cloud service, JetBrains manages remediation for the hosted service; users should verify with JetBrains that their instance is updated accordingly.

Description

A vulnerability in JetBrains TeamCity before versions 2026.1.4 and 2025.11.8 allows disclosure of access keys for parent project AWS connections. This issue is classified as CWE-201, involving insertion of sensitive information into sent data. The flaw can lead to exposure of highly sensitive credentials without user interaction.

References

Community reviews

Loading reviews…