TeamCity CVE-2026-132891 (CVSS 9.8): JetBrains Discloses 200+ Flaws at Once, Including Unauthenticated RCE via External Pull Requests and 10 Kotlin DSL Sandbox Escapes: Upgrade to 2026.2.2 or 2026.1.6

DevSecOps · 2026-11-21 · By H.A

TeamCity CVE-2026-132891 (CVSS 9.8): JetBrains Discloses 200+ Flaws at Once, Including Unauthenticated RCE via External Pull Requests and 10 Kotlin DSL Sandbox Escapes: Upgrade to 2026.2.2 or 2026.1.6

JetBrains published 202 TeamCity CVEs on 18–19 November, led by an unauthenticated pull-request RCE, so any server not on 2026.2.2 or 2026.1.6, including every 2025.11 install, should be upgraded now.

JetBrains has published about 200 CVEs for its TeamCity CI/CD server in two days. The most serious, CVE-2026-132891 (CVSS 9.8), allows remote code execution through external pull requests with no login and no user interaction. Alongside it come dozens of other code-execution flaws in the Kotlin DSL sandbox, VCS root handling and build settings.

The fixes are not brand new. They shipped quietly in the September, October and early-November releases. What is new is the public disclosure: anyone can now see exactly which TeamCity features were broken and which builds fix them. That makes every server still on an older build a much easier target.

What Happened

On 18 November, JetBrains published 21 TeamCity CVEs. Another 181 followed on 19 November, the first batch at 14:32 Mauritius time (10:32 UTC). By NVD's count, that is 202 TeamCity CVEs in two days. Of these, 36 describe remote code execution and around 90 are cross-site scripting issues. The rest cover privilege escalation, secret and token exposure, SSRF, XXE and authorization bypasses.

The CVEs line up with four rounds of bug-fix releases. JetBrains' release notes give the security count for each:

JetBrains' release notes say security bulletins are "typically published few days after the release date". This time the CVE records arrived weeks to months after the fixes.

Technical Details

According to the CVE record, CVE-2026-132891 affects TeamCity before 2026.2, 2026.1.4 and 2025.11.8. Its one-line description says remote code execution "was possible via external pull requests". The vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N, which means network access, low complexity, no privileges and no user interaction. It is classed as CWE-696 (Incorrect Behavior Order), which usually means a check runs too late or in the wrong sequence.

JetBrains has not published any further technical detail. In practice, pull-request building lets TeamCity fetch and build code from branches it does not control, often from forks on GitHub, GitLab or Bitbucket. A flaw at that boundary means a stranger who can open a pull request against a public repository may be able to reach code execution on the build infrastructure.

The other critical and high-severity code-execution bugs fall into a few groups:

Is It Being Exploited?

No exploitation has been reported for the new CVEs. On 19 November, CISA's vulnerability enrichment for CVE-2026-132891 recorded "Exploitation: none". It also marked the flaw "Automatable: yes", with a "Technical Impact: total".

The risk is still high. TeamCity bugs have a long record in CISA's Known Exploited Vulnerabilities catalog: CVE-2023-42793 (2023), CVE-2024-27198 (2024), CVE-2024-27199 (added April 2026) and CVE-2026-63077. CVE-2026-63077 is an unauthenticated RCE in the agent polling protocol, added to the catalog on 5 August 2026. Build servers hold signing keys, cloud credentials and deployment tokens, so state-backed and criminal groups move quickly once details are public.

Who Is Affected

What To Do Now

# Version from the REST API (needs a read token)
curl -s -H "Authorization: Bearer $TC_TOKEN" https://teamcity.example.internal/app/rest/server/version

# Look for unexpected VCS root and settings changes in the audit log
curl -s -H "Authorization: Bearer $TC_TOKEN" \
  "https://teamcity.example.internal/app/rest/audit?locator=count:200" | grep -iE "vcsRoot|settings|pullRequest"

Why It Matters

A single CI/CD server often has the keys to every production environment and software release a company ships. JetBrains fixed these bugs before publishing them, which is the right order. But more than 200 CVEs released at once give attackers a detailed map of TeamCity's weak points, with known fixed versions to diff against. Teams that skipped the September to November bug-fix releases now face the same clock as everyone else, and the attackers' analysis has already started.

Sources

COMPUTE NODE · · --:--:--

Fresh cybersecurity news,
daily threat intelligence.

Daily cyber news, live threat intel and exploited CVEs.

Everything in one place

Self-hosted, hardened, and yours.

RUN IT

Local AI console

Chat with a model on your own hardware via Ollama or any OpenAI-compatible server. No cloud, no key.

DEFEND

Cyber threat feed

Automatic daily intel from CISA KEV, NVD & GitHub advisories, a live cyber threat map, and your own notes.

NEWS

News & videos

Articles and updates on pentesting, AI, and cyber — with embedded video, including YouTube. Post your own.

DIRECTORY

Registry

Runtimes, models, MCP servers, agents, and a full security & pentest tooling section.

PUBLISH

Posts

Write, edit, publish, and share articles backed by a real database and your account.

COMMUNITY

Forum

Threads and replies across categories from Models to Hardware to Security.

CODE

Repos

Curated AI and security GitHub repos, plus a shelf for pinning your own.

DOWNLOAD

Skill packs

Agent starters, RAG scaffolds, and defensive security & VAPT report templates.

Registry

Runtimes, models, MCP servers, agent frameworks, and a security & pentest tooling section — all links out to the real projects.

Local AI console

Talk to a model running on your own machine through Ollama or an OpenAI-compatible server — your prompts and the model's replies always go straight from your browser to your local model, never through a Reef server. Attach files for context, and pick up saved chats where you left off.

Type /image a prompt in the box below to generate
Not connected

Local AI hardware benchmark

A spec-based compatibility advisor — tells you which local models your hardware can run well, which will be slow, and which to skip. Connect to Ollama below for a real, measured speed test instead of an estimate.

1. Your hardware

2. Live check against your local model server (optional)

If a local model server is running, this cross-references the table above with what you've actually got loaded — and runs a real, measured speed test instead of an estimate.

AI Database

A browsable catalog of AI models across providers — context windows, pricing, and capabilities.

Loading…

Cyber threat feed

Latest threats pulled automatically every day from CISA's Known-Exploited-Vulnerabilities catalog and NVD — plus threat intel you post yourself.

⇩ Export STIX
Loading threat feed…

Cyber threat map

Attacks happening right now, all over the world.

Connecting…
LIVE · MAURITIUS TIME--:--:--
attack route, country to country attack route into Mauritius attacker reported worldwide
Loading live data…
attackers reported per minute · click to rewindnow

Top attack routesweb

Attackers based inlast hour

Networkslast hour

Click any dot, feed row or table row to see that IP's profile.

Mauritius

Who attacks Mauritius

Loading…

Web attacks malicious requests to Mauritian websites that were blocked
Network DDoS floods meant to knock Mauritian servers offline

    Mauritius · last 24 h

    How Mauritius is attacked

    Network-level attacks (DDoS) aimed at Mauritius, by method. They try to knock servers and networks offline by sheer volume.

    • Loading…

    The ports or services these floods aimed at aren't published.

    Mauritius · last hour

    Attackers located in Mauritius

    0attackers located in Mauritius were reported in the last hour

    This counts attacks coming from Mauritius, not attacks on it: IPs in Mauritius that servers elsewhere reported for attacking them. Usually zero or one; when it rises, it's often a hacked local server or router.

    Worldwide today

    What attackers are knocking on

    Ports most targeted across a worldwide network of sensors .

    Worldwide today

    Most active attackers

    Ranked by how many separate sensors they hit. Click a row for its profile.

    IPCountryNetworkSensors hitReports
    What you're looking at
    Blue routes

    Share of attack traffic from one country to another. Thicker, faster streams carry more. Particles show volume, not one per attack.

    Every 15 min · published 1–2 h behind
    Amber flashes

    An attacking IP that servers around the world reported in the last minute, placed where the IP is. Its targets aren't published, so there's no line.

    Every minute · shown about 1 min behind
    Locations

    IP locations are approximate (city level at best) and show where the machine is hosted, not who controls it.

    Approximate · city level at best

    News

    Articles, guides and updates on pentesting, AI, and cybersecurity — with embedded video. Add your own, including YouTube.

    Loading…

    Posts

    Loading…

    Loading posts…

    Forum

    Questions, answers, and talk about running AI locally.

    Loading forum…

    GitHub repositories

    Curated AI and security repos, plus your own pinned shelf.

    Command board

    One-liners, configs, and advice worth keeping — shared by everyone here.

    ⚠ Commands are shared with all users. Never include credentials, tokens, or internal hostnames. Review anything before you run it.
    Loading commands…

    Skill packs

    Starter files served from the API — AI agent scaffolds plus defensive security & VAPT reporting templates. Click to download.

    Loading skills…

    Your watchlist

    Follow threat actors, malware, CVEs and vendors — we tell you when a new report, CVE record or exploitation alert mentions them.

    Threat Library

    Threat actors, malware and tools — their attack techniques, Reef Sentinel coverage and indicators of compromise.

    Loading…

    Threat Intelligence

    Curated threat write-ups, advisories and analysis — with cover media.

    Loading…

    Tutorials

    Step-by-step guides for running local AI, using the console, and tracking threats. Admins can add their own.

    Loading…

    Downloads

    Direct links to the official homepage/download page for well-known cybersecurity, penetration-testing, and local-AI software. Always verify checksums/signatures from the vendor before running anything.

    Loading…

    Privacy Policy

    Loading…

    Terms & Conditions

    Loading…

    Help & FAQ

    Answers to common questions about Reef Sentinel, plus a formatting guide for posts, articles, and comments.


    Formatting guide

    Commands you can type into the body of a post, comment, or reply — no HTML needed. Comments and short replies only support bold, italic, and inline code.

    Contact us

    Questions, feedback, or a security disclosure? Reach us directly, or send a message and we'll get back to you by email.

    Loading…

    Send a message

    VAPT Report Generator

    Build an engagement, add findings with a live CVSS calculator, and generate a branded, print-ready report.

    Recon Toolkit

    Investigate any domain, IP, URL, file hash, email or CVE in one search, plus breach and password checks, hash identification and a payload cheatsheet.

    Outage Monitor

    Is Microsoft 365, Facebook, Google, AWS or ChatGPT down? Live status of the big tech services from their official status pages, every incident with its full timeline, and how long each one took to fix.

    Website Checker

    Reads a website's HTTP response headers to identify its framework and server, shows any known CVEs for the exposed versions with details, and recommends what to do.

    Control panel

    Manage everything shown on the site — news & videos, posts, homepage headlines, and subscribers. Admin only.

    Overview
    Content
    Site
    Account & Security

    Email settings

    SMTP on ports 25/465/587 is blocked outbound by some hosts (e.g. DigitalOcean droplets by default) — Resend and Brevo send over their HTTPS API instead, so they work even then. Only the selected provider is used to send; the others stay saved but idle, so you can switch back any time without losing settings.

    Get a key from resend.com/api-keys. Uses the "From address" below as the sender — it must be on a domain you've verified with Resend.

    Get an API key (not an SMTP key) from app.brevo.com/settings/keys/api. Uses the "From address" below as the sender — it must be a verified sender in your Brevo account.

    "From address" and "Site name/URL" are shared by SMTP, Resend, and Brevo — they control what recipients see, regardless of which provider is active.

    Send a test email

    Sends through whichever provider is currently active above. Save your settings first if you just changed them.

    SIGNAL LOST

    We couldn't find this page

    The page may have been moved or deleted, or the address was mistyped.