Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-63077 – Unauthenticated RCE via Agent Polling Protocol – JetBrains TeamCity before 2026….

Be the first to know when new zero-days emerge:

Summary

CVE-2026-63077 is a critical unauthenticated remote code execution vulnerability in JetBrains TeamCity On-Premises, stemming from insecure deserialization of untrusted data (CWE-502) in the agent polling protocol. It affects all TeamCity On-Premises versions prior to 2026.1.3 and 2025.11.7, and carries a CVSS v3.1 base score of 9.8 (Critical). An unauthenticated remote attacker can exploit this flaw to execute arbitrary code on the TeamCity server with no credentials or user interaction required.

Technical details

  • Root cause: Deserialization of untrusted data (CWE-502) in TeamCity’s agent polling protocol — the communication channel used by build agents to poll the TeamCity server for jobs and configuration updates.
  • Trigger conditions: An attacker sends a crafted, malicious payload to the agent polling endpoint exposed over the network; no authentication, session token, or valid username is required.
  • Attack vector: Fully remote, over the network (AV:N). Attack complexity is low (AC:L), no privileges required (PR:N), no user interaction required (UI:N).
  • Impact: Full compromise of confidentiality, integrity, and availability — successful exploitation results in arbitrary code execution on the underlying server, enabling access to source code, build secrets, environment variables, CI/CD pipelines, and lateral movement through connected infrastructure.

Affected software

  • JetBrains TeamCity On-Premises — all versions before 2026.1.3 (2026.x branch)
  • JetBrains TeamCity On-Premises — all versions before 2025.11.7 (2025.11.x branch)

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade to TeamCity 2026.1.3 (if on the 2026.x branch) or TeamCity 2025.11.7 (if on the 2025.11.x branch), which contain the vendor-provided fix.
  • If immediate patching is not feasible: Restrict network access to the TeamCity server — particularly the agent polling port — to only trusted internal build agent IP ranges. Prevent any untrusted external network access to the TeamCity instance until the patch is applied.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge