cve.bz

CVE-2026-63077 JetBrains TeamCity Deserialization of Untrusted Data Vulnerability

9.8 criticalKEVExploitEPSS 95%

Critical (9.8) in JetBrains TeamCity. In CISA KEV since 2026-08-05, with known ransomware use. EPSS 95% estimated probability of exploitation activity in the next 30 days.

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

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
95% (unchanged from 95% a week ago; 90% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2026-08-05, due 2026-08-08, known ransomware use
CISA's assessment (SSVC)
Exploitation: active · Automatable: yes · Technical impact: total, assessed 2026-07-27. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-63077 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-63077?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-63077?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-63077 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
JetBrains TeamCitybefore 2026.1.3, 2025.11.7

Public exploits

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • sfewer-r7/CVE-2026-63077 Harbor Check: matches CVE 20 stars, Python, created
    Unauthenticated Remote Code Execution in JetBrains TeamCity (CVE-2026-63077)
  • basesixtythree/B63-POC-CVE-2026-63077 Harbor Check: matches CVE 0 stars, Python, created
    PoC and verification material for CVE-2026-63077 (JetBrains TeamCity agent-polling deserialization RCE)
  • 0xCyp1337/CVE-2026-63077 Harbor Check: matches CVE 0 stars, Python, created
    CVE-2026-63077 - Unauthenticated RCE exploit for JetBrains TeamCity via Agent Polling Deserialization. Supports mass scanning, multi-thread…
  • AnggaTechI/CVE-2026-63077 Harbor Check: matches CVE 0 stars, Python, created
    CVE-2026-63077 — Unauthenticated Remote Code Execution in JetBrains TeamCity via agent polling protocol deserialization. CVSS 9.8 CRITICAL.…
  • bakos-sandor-nx/teamcity-cve-2026-63077-remediation 0 stars, created
    JetBrains TeamCity On-Premises CVE-2026-63077 Emergency Hardening & Patch Runbook Package
2 more

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON