Skip to main content
CVE-2026-63077VulnerabilityPublished Updated

CVE-2026-63077: JetBrains TeamCity · CWE-502

Affects JetBrains TeamCitySource CVE Database V5

0

Exploited in the wild · used in ransomware campaigns · KEV due 8 Aug 2026 · public exploit available (Metasploit) · 93% EPSS : upgrade to 2026.1.3 now.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
KEV deadline
 US federal agencies must patch by this date; a sensible deadline for everyone else.
Ransomware
Used in ransomware campaigns
EPSS
93.5% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.1.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 27 Jul 2026

  2. Weaponised: evidence found.

    1 Metasploit module

  3. Exploited in the wild: evidence found.

    Listed in CISA KEV 9 days after disclosure

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

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by JetBrains

    , 12 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , 23 minutes after disclosure

  4. Added to CISA KEV (opens in a new tab)

    exploitation confirmed · ransomware use known

    , 9 days after disclosure

  5. KEV remediation due

    US federal deadline

    , 12 days after disclosure

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

What to do

Upgrade JetBrains TeamCity to 2026.1.3.

Affected software

ProductAffectedFixed in
JetBrainsTeamCityAffected
  • =0
Fixed in
  • 2026.1.3

Description

In JetBrains TeamCity before 2026.1.3, 2025.11.7 unauthenticated remote code execution was possible via the agent polling protocol

References

Community reviews

Loading reviews…