What is CVE-2026-63077?

CVE-2026-63077 is JetBrains TeamCity Deserialization of Untrusted Data Vulnerability. The supplied enrichment data classifies it as Deserialization mapped to CWE-502 Deserialization of Untrusted Data.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

16 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, EDR process telemetry, host service logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-63077 using CVSS 9.8, EPSS 1%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVcriticalDeserializationpublic exploit

CVE-2026-63077

JetBrains TeamCity Deserialization of Untrusted Data Vulnerability

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2026-63077 in CISA KEV with required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

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

Published Jul 27, 2026Updated Aug 6, 2026Sources: NVD, JetBrains (CNA), CISA, FIRST EPSS, GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Aug 5, 2026

EPSS

ahead of 60% of scored CVEs

Affects

JetBrains

TeamCity

CVSS base

9.8

critical

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade TeamCity to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Federal deadline Aug 8, 2026 — passed 17 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
JetBrains	TeamCity	0 to < 2026.1.3, 2025.11.7	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
9.8	CVSS 3.1	critical	3.9	5.9	JetBrains (CNA), GHSA

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-502 · Deserialization of Untrusted Data

Modify Application Data
Unexpected State
DoS: Resource Consumption (CPU)
Varies by Context

Mitigation: If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.

Weakness & attack patterns

CWE-502Deserialization of Untrusted Data

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-586 · Object Injection

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Aug 5, 2026

Federal deadline

Aug 8, 2026

passed 17 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Exploit entries

Exploit-DB and CTI exploit indexes

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

35 more posts on this CVEShowing 5 of 40 · Who is discussing this CVE, and how loudlyUnlock free

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable TeamCity.
Monitor for scanner or exploit-pattern traffic after 16 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSEDR process telemetryhost service logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Cve is exploited AnggaTechI/CVE-2026-63077
Aug 8, 2026 · SOCRadar CTI
Cve is exploited BoredHackerBlog/teamcity-CVE-2026-63077-pcap
Aug 8, 2026 · SOCRadar CTI
Added · CVSS 3.1 9.8 (AV:N)
Aug 6, 2026 · NVD
Added to CISA KEV catalog
Aug 5, 2026 · CISA
Initial · CVE published
Jul 27, 2026 · NVD
Added · GHSA-94gx-v738-fx9w published (critical)
Jul 27, 2026 · GitHub Security Advisory

Source activity

Readings a source repeats on a schedule, counted rather than listed.

10×SvrsJul 29, 2026 – Aug 9, 2026 · SOCRadar CTI
9×TweetsJul 30, 2026 – Aug 9, 2026 · SOCRadar CTI
6×ModifiedAug 5, 2026 – Aug 6, 2026 · SOCRadar CTI
4×Github ReposJul 30, 2026 – Aug 8, 2026 · SOCRadar CTI
3×TelegramAug 6, 2026 – Aug 9, 2026 · SOCRadar CTI
1×CVE appeared in the Cve Trends.Jul 29, 2026 · SOCRadar CTI

References

7 on the record

www.jetbrains.com/privacy-security/issues-fixed/
Vendor Advisory, NIST
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-63077
US Government Resource, NIST
nvd.nist.gov/vuln/detail/CVE-2026-63077
NVD, Vendor Advisory
github.com/advisories/GHSA-94gx-v738-fx9w
Exploit, Third Party Advisory
blog.jetbrains.com/teamcity/2026/07/cve-2026-63077/
Vendor Advisory
www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
US Government Resource
www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
US Government Resource

Coverage

22 stories from the feeds we poll

17 more reports on this CVEShowing 5 of 22 · Vendor research and security press coverageUnlock free

Elsewhere on this site

JetBrainsevery CVE for this vendor
August 2026what else CISA listed
Deserializationsame class
CWE-502other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-63077 is JetBrains TeamCity Deserialization of Untrusted Data Vulnerability, a critical vulnerability affecting TeamCity from JetBrains. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 16 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.8 describes technical severity, while EPSS 1% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.