Skip to main content
CVE-2026-132248VulnerabilityPublished

In JetBrains TeamCity before 2026.1.3 improper authorization allowed project viewers to change project IDs

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-132248· Medium 5.4

Not known to be exploited · CVSS 5.4 Medium : upgrade to 2026.1.3 when convenient.

Data as of 18 Nov 2026, 20:05 UTC

CVSS 3.1 base score
5.4Medium
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.15.4
Patch
Available – fixed in 2026.1.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 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 17 Nov 2026.

What to do

Upgrade TeamCity and org.jetbrains.teamcity/teamcity-server to 2026.1.3.

Affected software

ProductAffectedFixed in
JetBrainsTeamCityAffected
  • <2026.1.3
Fixed in
  • 2026.1.3
Mavenorg.jetbrains.teamcity/teamcity-serverpkg:maven/org.jetbrains.teamcity/teamcity-serverOther threatsAffected
  • <2026.1.3
Fixed in
  • 2026.1.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in JetBrains TeamCity version 2026.1.3. Users should upgrade to this version or later to remediate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

A vulnerability in JetBrains TeamCity versions before 2026.1.3 allows users with project viewer permissions to improperly change project IDs due to insufficient authorization checks.

References

Community reviews

Loading reviews…