CVE-2026-63077

CVE-2026-63077 is a critical-severity vulnerability in Jetbrains Teamcity with a CVSS 3.x base score of 9.8. It is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, confirming it has been exploited in the wild (added 2026-08-05). The underlying weakness is classified as CWE-502.

Key facts

Description

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

Frequently asked questions

What is CVE-2026-63077?
In JetBrains TeamCity before 2026.1.3, 2025.11.7 unauthenticated remote code execution was possible via the agent polling protocol
How severe is CVE-2026-63077?
CVE-2026-63077 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-63077 being actively exploited?
Yes. CVE-2026-63077 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2026-08-05, which means active exploitation has been confirmed. It should be prioritised for remediation.
What products are affected by CVE-2026-63077?
CVE-2026-63077 affects Jetbrains Teamcity. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-63077?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.
When was CVE-2026-63077 published?
CVE-2026-63077 was published on 2026-07-27 and last updated on 2026-08-06.

References

Affected products (1)

More vulnerabilities in Jetbrains Teamcity

All CVEs affecting Jetbrains Teamcity →

Other CWE-502 (Deserialization of Untrusted Data) vulnerabilities

Browse all CWE-502 (Deserialization of Untrusted Data) vulnerabilities →

Threat intelligence

Threat-intel indicators referencing this CVE: