Return to Threats

Critical TeamCity Flaw Could Let Attackers Run OS Commands Without Logging In

thehackernews.com 2026-07-28 AI supply chain Critical

What Happened

JetBrains is urging customers of on-premise versions of TeamCity to update to the latest version following the discovery of a critical security issue that could result in arbitrary code execution. The vulnerability, assigned CVE-2026-63077 (CVSS score: 9.8), affects all TeamCity On-Premises versions. It has been addressed in versions 2025.11.7 and 2026.1.3. TeamCity Cloud instances have already

Why It Matters

The article reports a critical unauthenticated remote code execution vulnerability (CVE-2026-63077, CVSS 9.8) in JetBrains TeamCity On-Premises, allowing attackers to run OS commands without logging in; JetBrains has patched the flaw in versions 2025.11.7 and 2026.1.3. This continues a pattern of severe TeamCity issues, where prior auth-bypass and RCE flaws such as CVE-2024-27198 enabled complete compromise of CI/CD servers and software build pipelines.[7][8] From a RealGround perspective, compromise of TeamCity directly impacts the software supply chain for AI systems, as malicious code, models, or dependencies can be injected at build time, undermining integrity of AI services. Organizations should treat TeamCity as critical supply-chain infrastructure, enforce rapid patching and network hardening, and integrate SBOM-based monitoring and CI/CD hardening into AI governance and security programs.

Healthcare Fintech SaaS SMB AI startups

RealGround Analysis

This signal maps to AI supply chain. Organizations using AI agents, LLM APIs, SaaS integrations, or sensitive data workflows should review whether this class of issue could create unauthorized tool execution, data leakage, weak approval gates, or unmanaged supply-chain exposure.

Recommended Actions

  • Restrict AI agent tool permissions and production write paths.
  • Review sensitive data access across prompts, logs, embeddings, memory, and SaaS integrations.
  • Add human approval workflows for high-impact or state-changing actions.
  • Run prompt injection and indirect prompt injection tests against affected workflows.
  • Document the owner, control gap, and remediation deadline for this risk class.

Source

https://thehackernews.com/2026/07/critical-teamcity-flaw-could-let.html

Talk to AI CISO