JetBrains Patches Critical Exposed SQL Injection and TeamCity Flaws

JetBrains fixed CVE-2026-108474, a CVSS 9.8 SQL injection in Exposed, and two TeamCity flaws, CVE-2026-106218 and CVE-2026-106219; no exploitation reported.
Table of Contents
    Add a header to begin generating the table of contents

    JetBrains has released fixes for three vulnerabilities, led by CVE-2026-108474, a critical unauthenticated SQL injection in the Exposed framework rated CVSS 9.8. Two TeamCity flaws were patched in the same advisories. As of October 10, no exploitation had been confirmed.

    CVE-2026-108474: Unauthenticated SQL Injection in Exposed

    The Exposed framework fails to escape string arguments in several SQL functions, which allows unauthenticated SQL injection. Versions before 1.5.1 are affected. The fix is to upgrade to Exposed 1.5.1.

    Applications that use the library could face data theft or code execution, according to the impact described in the advisory coverage.

    Two TeamCity Flaws Fixed in Separate Release Lines

    The TeamCity vulnerabilities affect build servers, and each has its own affected-version range.

    CVE-2026-106218: Git Submodule URL Validation (CVSS 8.8)

    CVE-2026-106218, rated CVSS 8.8 and classified as CWE-184, is an improper validation of Git submodule URLs in TeamCity. It enables repository access. TeamCity versions before 2026.2.1 are affected, and upgrading to 2026.2.1 resolves it.

    CVE-2026-106219: Kotlin DSL Sandbox Escape (CVSS 6.5)

    CVE-2026-106219, rated CVSS 6.5 and classified as CWE-73, is a Kotlin DSL sandbox escape that permits arbitrary code execution. It affects TeamCity before 2026.1.3 and before 2025.11.7, depending on the release line. Fixes are in 2026.1.3 and 2025.11.7.

    Patch Targets and Exploitation Status

    The three fixes are Exposed 1.5.1, TeamCity 2026.2.1 for the Git submodule flaw, and TeamCity 2026.1.3 or 2025.11.7 for the Kotlin DSL sandbox escape. The advisories and patches were published on October 10.

    No exploitation had been confirmed as of that date. The coverage does not say whether proof-of-concept code exists for any of the three flaws.

    Data Theft in Exposed Apps, Code Execution on TeamCity Servers

    The impact is that build servers and applications using Exposed could face data theft or code execution. For TeamCity, the submodule flaw exposes repository access and the sandbox escape exposes code execution on the build server.

    The three CVEs sit at different severity levels: 9.8 for the Exposed injection, 8.8 for the submodule validation flaw and 6.5 for the sandbox escape. The Exposed flaw carries the highest score and requires no authentication. It sits in a library that other applications embed, so each application using an affected version inherits the exposure.

    The version ranges differ among the products. Teams on the TeamCity 2026.1 line need 2026.1.3 for the Kotlin DSL fix, while teams on the 2025.11 line need 2025.11.7, and the Git submodule fix is delivered in 2026.2.1. The coverage does not state whether the Git submodule flaw has a fix for the older lines.

    Advisory Details by Product

    The three advisories cover two JetBrains products. The Exposed framework, a Kotlin library, is addressed by a single critical fix. TeamCity, JetBrains’ build and continuous integration server, receives two fixes with different severity ratings and different fixed versions.

    For the Exposed flaw, the advisory describes string arguments that several SQL functions do not escape. An attacker who can supply such a string to an application using the affected functions can inject SQL without authenticating. This explains the 9.8 CVSS rating.

    The TeamCity Git submodule flaw, CVE-2026-106218, is categorized as CWE-184, and the Kotlin DSL sandbox escape, CVE-2026-106219, as CWE-73. Both fixes were published with the Exposed fix on October 10.

    No Confirmed Exploitation of the Three JetBrains Flaws as of October 10

    The advisories and patches were published on October 10, and no exploitation had been confirmed as of that date. The coverage describes the practical exposure in two groups: applications that embed Exposed before 1.5.1, where the unauthenticated injection could lead to data theft, and TeamCity servers below the fixed versions, where repository access and arbitrary code execution are possible through the two separate flaws.

    TeamCity servers sit in the build pipeline, so code execution there reaches the systems that compile and package software. The coverage lists the impact in general terms and does not describe any attack using the three flaws.

    Related Posts