critical

CVE

CVE-2026-123317, CVE-2026-121819, CVE-2026-121820, CVE-2026-121821, CVE-2026-121822, CVE-2026-121823, CVE-2026-121824, CVE-2026-11749, CVE-2026-123276, CVE-2026-123279, CVE-2026-123280, CVE-2026-123281, CVE-2026-123293, CVE-2026-123294, CVE-2026-123295, CVE-2026-123296, CVE-2026-123301, CVE-2026-123302, CVE-2026-123304, CVE-2026-123305, CVE-2026-123321, CVE-2026-123323

CWE

CWE-347, CWE-565, CWE-22, CWE-409, CWE-770, CWE-79, CWE-94

Affected Surface

  • Maven `io.ktor:ktor-server-sessions` / `ktor-server-sessions-jvm` versions `< 3.6.1` (`CVE-2026-123317` / `KTOR-9477`, CVSS 8.1 High, fixed in `3.6.1`)
  • Maven `com.linecorp.armeria:armeria`, `armeria-saml`, `armeria-thrift`, `armeria-xds`, `armeria-jetty*`, and `armeria-tomcat*` versions `< 1.43.0` (`CVE-2026-121819` through `CVE-2026-121824`, CVSS up to 8.7 High, fixed in `1.43.0`; plus `CVE-2026-11749` in `armeria-saml < 1.41.1`)
  • JetBrains IDEs opening untrusted repositories: IntelliJ IDEA `< 2026.3` / `< 2026.2.4` (`CVE-2026-123293`, `CVE-2026-123302`, `CVE-2026-123304`, `CVE-2026-123305`, `CVE-2026-123301`), CLion `< 2026.3` / `< 2026.2.4.1` (`CVE-2026-123276`), and WebStorm `< 2026.3` / `< 2026.2.3` (`CVE-2026-123321`)
  • JetBrains Datalore `< 2026.4` / `< 2026.2.4` (`CVE-2026-123279` CVSS 9.0 Critical, `CVE-2026-123280` CVSS 8.1 High, `CVE-2026-123281` CVSS 7.5 High) and JetBrains Hub `< 2026.2.52556` (`CVE-2026-123294` CVSS 9.6 Critical, `CVE-2026-123295` CVSS 8.1 High, `CVE-2026-123296` CVSS 7.5 High)

TL;DR

On 6 November 2026 (04:59 to 11:17 UTC), JetBrains and LY Corporation (LINE) published 24 security advisories spanning two core JVM web/RPC frameworks (JetBrains Ktor and LINE Armeria) and JetBrains’ developer IDE and data-science suite (IntelliJ IDEA, CLion, WebStorm, Datalore, and Hub):

  1. JetBrains Ktor < 3.6.1 encrypted session-cookie forgery via unauthenticated AES-CBC IV (CVE-2026-123317 / KTOR-9477, CVSS 8.1 High): In SessionTransportTransformerEncrypt, Ktor encrypted session payloads with AES/CBC/PKCS5Padding and formatted cookies as <iv_hex>/<encrypted_hex>:<mac_hex>, but computed the HmacSHA256 tag over encrypted alone (mac(encrypted)) without including iv (and prior to 5e938a9b6d9c compared hex MAC strings with non-constant-time ==). Because AES-CBC recovers the first 16-byte plaintext block as P_0 = Dec_K(C_0) XOR IV, any user who knows the first 16 bytes of their own serialized session ({"userId":42,...) can replace IV with IV XOR P_0 XOR P'_0 to rewrite the first 16 bytes of decrypted session state ({"userId": 1,...) while the ciphertext and its HMAC remain valid.
  2. LINE Armeria < 1.43.0 path-decorator auth bypass, SAML pre-signature DEFLATE bomb, Thrift OOM, xDS symlink escape, and CORS / FileService flaws (CVE-2026-121819 through CVE-2026-121824, plus CVE-2026-11749):
    • CVE-2026-121823 (GHSA-xqhm-4ph4-423v, CVSS 8.7 High): DefaultRequestTarget rejected .. segments but left single-dot segments (/./admin/x, /%2e/admin/x, and /.;a=b/admin/x) un-normalized during routing and decorator matching. An unauthenticated request to /./admin/secret skipped sb.decoratorUnder("/admin", authDecorator) and was then normalized to /admin/secret by FileService, TomcatService, or JettyService.
    • CVE-2026-121820 (GHSA-6hgp-j5h7-33m3, CVSS 8.7 High) and CVE-2026-11749 (GHSA-v86g-h7gx-q845, CVSS 7.6 High): In armeria-saml, HttpRedirectBindingUtil.fromDeflatedBase64() inflated SAMLRequest / SAMLResponse query parameters into an unbounded ByteArrayOutputStream before verifying the SAML signature (CVE-2026-121820), allowing a few kilobytes of compressed zeros to exhaust JVM heap; additionally, armeria-saml < 1.41.1 did not enforce one-time use of bearer assertion IDs (CVE-2026-11749).
    • CVE-2026-121824 (GHSA-2pfv-5p52-crjm, CVSS 8.7 High), CVE-2026-121819, CVE-2026-121821 (GHSA-386q-mrg6-jfj8), and CVE-2026-121822 (GHSA-x9vf-hjgg-cq25): armeria-thrift allocated field and container buffers before checking readable bytes (CVE-2026-121824); armeria-xds DataSourcePolicy.isFileAllowed checked paths lexically while FileWatcher followed symlinks outside allowed roots, bypassing the 1.40.0 fix for CVE-2026-11752 (CVE-2026-121819); CorsConfig.getPolicy() ignored route() restrictions on any-origin (*) policies even with allowCredentials() enabled (CVE-2026-121821); and AutoIndex.listingToHtml() rendered unescaped filenames into directory listings (CVE-2026-121822).
  3. JetBrains IntelliJ IDEA, CLion, and WebStorm Safe Mode / untrusted-project RCEs (CVE-2026-123293, CVE-2026-123302, CVE-2026-123304, CVE-2026-123305, CVE-2026-123276, CVE-2026-123321) plus Datalore and Hub (CVE-2026-123279, CVE-2026-123280, CVE-2026-123294): Opening an untrusted repository in IntelliJ IDEA (< 2026.3 / < 2026.2.4), CLion (< 2026.3 / < 2026.2.4.1), or WebStorm (< 2026.3 / < 2026.2.3) executed attacker-controlled binaries or tasks via workspace-configured Terraform paths (CVE-2026-123293), script engine discovery (CVE-2026-123302), ShellCheck paths (CVE-2026-123304), CLion GDB server debug profiles in Safe Mode (CVE-2026-123276), WebStorm Grunt/Gulp task loading (CVE-2026-123321), and Dev Container archive extraction (CVE-2026-123305). Meanwhile, JetBrains Datalore < 2026.4 allowed view-only collaborators (CVE-2026-123279, CVSS 9.0) and unauthenticated interactive-report viewers (CVE-2026-123280, CVSS 8.1) to execute arbitrary notebook code, and JetBrains Hub < 2026.2.52556 allowed account takeover by swapping email authentication details mid-verification (CVE-2026-123294, CVSS 9.6).

What to do now: Upgrade Ktor to >= 3.6.1 (and leave backwardCompatibleRead = false), upgrade Armeria to >= 1.43.0, and update IntelliJ IDEA, CLion, WebStorm, Datalore, and Hub to the 2026.3 / 2026.2.4+ / 2026.4 builds. Rotate Ktor session encryption and signing keys if SessionTransportTransformerEncrypt was exposed to untrusted clients.

Affected packages and products

EcosystemPackage / ProductCVE / AdvisorySeverityAffected versionsFixed versionVulnerable component
Maven (Kotlin / JVM)io.ktor:ktor-server-sessions (ktor-server-sessions-jvm)CVE-2026-123317 (KTOR-9477)CVSS 8.1 High< 3.6.13.6.1SessionTransportTransformerEncrypt.kt
Maven (Java / JVM)com.linecorp.armeria:armeriaCVE-2026-121823 (GHSA-xqhm-4ph4-423v), CVE-2026-121821 (GHSA-386q-mrg6-jfj8), CVE-2026-121822 (GHSA-x9vf-hjgg-cq25)CVSS 8.7 High / Medium< 1.43.0 (0.84.0..1.42.0 for 121821; 0.80.0..1.42.0 for 121822)1.43.0DefaultRequestTarget.java, CorsConfig.java, AutoIndex.java
Maven (Java / JVM)com.linecorp.armeria:armeria-samlCVE-2026-121820 (GHSA-6hgp-j5h7-33m3), CVE-2026-11749 (GHSA-v86g-h7gx-q845)CVSS 8.7 High / 7.6 High< 1.43.0 (121820); < 1.41.1 (11749)1.43.0 / 1.41.1HttpRedirectBindingUtil.fromDeflatedBase64(), SamlAssertionConsumerFunction.java
Maven (Java / JVM)com.linecorp.armeria:armeria-thrift, armeria-xdsCVE-2026-121824 (GHSA-2pfv-5p52-crjm), CVE-2026-121819CVSS 8.7 High / High< 1.43.0 (1.40.0..1.42.0 for 121819)1.43.0TByteBufTransport.java, DataSourcePolicy.java, FileWatcher.java
Developer IDEsJetBrains IntelliJ IDEA, CLion, WebStormCVE-2026-123293, CVE-2026-123302, CVE-2026-123304, CVE-2026-123305, CVE-2026-123276, CVE-2026-123321CVSS 7.5 to 7.8 HighIntelliJ < 2026.3 / < 2026.2.4; CLion < 2026.3 / < 2026.2.4.1; WebStorm < 2026.3 / < 2026.2.32026.3, 2026.2.4 (2026.2.4.1 CLion, 2026.2.3 WebStorm)Untrusted project / Safe Mode settings for Terraform, ShellCheck, script engines, GDB server profiles, Grunt/Gulp, and Dev Containers
AI / IAM ServersJetBrains Datalore, JetBrains HubCVE-2026-123279 (9.0), CVE-2026-123280 (8.1), CVE-2026-123281 (7.5), CVE-2026-123294 (9.6), CVE-2026-123295 (8.1)Critical / HighDatalore < 2026.4 (< 2026.2.4 for 123280); Hub < 2026.2.52556Datalore 2026.4 / 2026.2.4; Hub 2026.2.52556Notebook view-only / interactive report execution, mount broker, and Hub email verification / 2FA profile endpoints

Technical analysis

1. CVE-2026-123317 (KTOR-9477): First-block AES-CBC bit-flipping in Ktor SessionTransportTransformerEncrypt

When a Ktor application encrypts session cookies with SessionTransportTransformerEncrypt(encryptionKey, signKey), transformWrite() generates a random 16-byte AES-CBC initialization vector (iv), encrypts the UTF-8 serialized session string, and appends an HmacSHA256 signature (hex(iv) + "/" + hex(encrypted) + ":" + hex(hmac(encrypted))).

Prior to Ktor 3.6.1 (commit 0aaca706fe5b and 5e938a9b6d9c), transformWrite() and transformRead() passed only encrypted (C) to mac(), leaving iv completely outside the MAC calculation. Because CBC decryption computes the first 16-byte plaintext block as P_0 = AES_Dec(C_0) XOR IV and does not use IV for any subsequent block (P_i = AES_Dec(C_i) XOR C_{i-1} for i >= 1), mutating IV to IV' = IV XOR delta mutates P_0 to P_0 XOR delta without disturbing C_0, the PKCS#7 padding in the final block (whenever the ciphertext has at least two blocks, i.e., plaintext >= 16 bytes), or HMAC(C).

As Ktor’s own regression test in SessionTransportTransformerEncryptTest.kt demonstrates, if a 27-byte session serializes as {"userId":42,"role":"user"} (where the first 16 bytes are {"userId":42,"ro), an attacker holding their own valid cookie can XOR the 16-byte hex IV with {"userId":42,"ro XOR {"userId": 1,"ro to become userId: 1:

--- a/ktor-server/ktor-server-plugins/ktor-server-sessions/jvm/src/io/ktor/server/sessions/SessionTransportTransformerEncrypt.kt
+++ b/ktor-server/ktor-server-plugins/ktor-server-sessions/jvm/src/io/ktor/server/sessions/SessionTransportTransformerEncrypt.kt
@@ -91,15 +91,21 @@ public class SessionTransportTransformerEncrypt(
             val macHex = encryptedAndMac.substringAfterLast(':', "")
             val encrypted = encryptedAndMac.substringBeforeLast(':').hexToByteArray()
             val expectedMac = macHex.hexToByteArray()
-            val macCheck = MessageDigest.isEqual(mac(encrypted), expectedMac)
-            if (!macCheck && !backwardCompatibleRead) {
+            val iv = transportValue.substringBeforeLast('/').hexToByteArray()
+            if (iv.size != ivSize) {
                 return null
             }
 
-            val iv = transportValue.substringBeforeLast('/').hexToByteArray()
-            val decrypted = decrypt(iv, encrypted)
+            if (MessageDigest.isEqual(mac(authenticatedData(iv, encrypted)), expectedMac)) {
+                return decrypt(iv, encrypted).toString(charset)
+            }
+            if (!backwardCompatibleRead) {
+                return null
+            }
@@ -118,10 +124,13 @@ public class SessionTransportTransformerEncrypt(
         val iv = ivGenerator(ivSize)
         val decrypted = transportValue.toByteArray(charset)
         val encrypted = encrypt(iv, decrypted)
-        val mac = mac(encrypted)
+        val mac = mac(authenticatedData(iv, encrypted))
         return "${iv.toHexString()}/${encrypted.toHexString()}:${mac.toHexString()}"
     }
 
+    private fun authenticatedData(initVector: ByteArray, encrypted: ByteArray): ByteArray =
+        byteArrayOf(initVector.size.toByte()) + initVector + encrypted

Note that because Ktor 3.6.1 changes the MAC input to byteArrayOf(iv.size.toByte()) + iv + encrypted, upgrading to 3.6.1 invalidates pre-existing encrypted session cookies by default (forcing users to re-authenticate). Do not enable backwardCompatibleRead = true in production: while 3.6.1 also checks iv.size == ivSize, backwardCompatibleRead = true still accepts cookies authenticated with mac(encrypted) or mac(decrypted).

2. CVE-2026-121823 and CVE-2026-121820: Armeria /./ decorator bypass and SAML HTTP-Redirect DEFLATE bomb

In Armeria < 1.43.0, DefaultRequestTarget.slowForServer() called pathContainsDoubleDots() to reject /../, /.., and /.\\, but permitted single-dot segments (/./, /., /%2e/, and /.;a=b/ when allowSemicolonInPathComponent was enabled) without collapsing them. Because Armeria’s router and ServerBuilder.decoratorUnder("/admin", ...) match against the raw RequestTarget path, a request for GET /./admin/secret or GET /%2e/admin/secret did not match /admin/* and skipped the authentication decorator, after which FileService, TomcatService, or JettyService resolved . and served /admin/secret. Commit 1be57ba78683 replaces pathContainsDoubleDots() with pathContainsDotSegments(), rejecting any . or .. segment (including before ;) with 400 Bad Request.

In armeria-saml < 1.43.0 (CVE-2026-121820), HttpRedirectBindingUtil.toSamlObject() decoded the SAMLRequest or SAMLResponse query parameter by calling fromDeflatedBase64() before validateSignature():

--- a/saml/src/main/java/com/linecorp/armeria/server/saml/HttpRedirectBindingUtil.java
+++ b/saml/src/main/java/com/linecorp/armeria/server/saml/HttpRedirectBindingUtil.java
@@ -267,16 +272,27 @@ static String fromDeflatedBase64(String base64Encoded) {
-        final byte[] decoded;
+    static String fromDeflatedBase64(String base64Encoded, int maxInflatedLength) {
         try {
-            decoded = Base64.getDecoder().decode(base64Encoded);
+            final byte[] decoded = Base64.getDecoder().decode(base64Encoded);
+            final Inflater inflater = new Inflater(true);
+            try (InputStream in = new SizeEnforcingInputStream(
+                    new InflaterInputStream(new ByteArrayInputStream(decoded), inflater),
+                    maxInflatedLength,
+                    count -> new InvalidSamlRequestException(
+                            " the inflated SAML message exceeds the maximum allowed length (" +
+                            maxInflatedLength + "): " + count))) {
+                return new String(ByteStreams.toByteArray(in), StandardCharsets.UTF_8);
+            } finally {
+                inflater.end();
+            }

Because fromDeflatedBase64() previously piped the base64-decoded bytes through an unbounded InflaterOutputStream(new ByteArrayOutputStream()), an unauthenticated request to any SAML SSO or SLO redirect endpoint could supply a few kilobytes of DEFLATE-compressed zeros that inflated into gigabytes on the JVM heap. Commit ed4b7a317503 wraps the InflaterInputStream in SizeEnforcingInputStream with a 1 MiB default ceiling (DEFAULT_MAX_INFLATED_MESSAGE_LENGTH).

Indicators of compromise (IOCs) and exploit patterns

  • Armeria CVE-2026-121823 access-log patterns: HTTP requests containing /./, /%2e/, /%2E/, /.;, or /..; targeting path-protected prefixes.
  • JetBrains IDE untrusted-project persistence files (CVE-2026-123293, CVE-2026-123302, CVE-2026-123304, CVE-2026-123276, CVE-2026-123321): .idea/terraform.xml, .idea/shellcheck.xml, .idea/workspace.xml, .idea/runConfigurations/*.xml (GDB server debug profiles), or .devcontainer/devcontainer.json inside cloned repositories pointing tool paths at repo-relative binaries or scripts.

Detection and remediation

# 1. Find vulnerable Ktor and Armeria versions in Gradle and Maven projects
rg -n '(io\.ktor:ktor-server-sessions|com\.linecorp\.armeria:armeria)' \
  build.gradle* gradle/libs.versions.toml pom.xml 2>/dev/null

# 2. Scan cloned repositories for weaponized .idea tool paths before opening in JetBrains IDEs
rg -n '(terraformPath|shellcheck|GDBServer|Grunt|Gulp)' .idea/ 2>/dev/null || true
  1. Upgrade Ktor to >= 3.6.1 and rotate session keys: Update io.ktor:ktor-server-sessions to 3.6.1, keep backwardCompatibleRead = false, and rotate the SecretKeySpec keys passed to SessionTransportTransformerEncrypt.
  2. Upgrade LINE Armeria to >= 1.43.0: Update all com.linecorp.armeria:* artifacts to 1.43.0. If allowSemicolonInPathComponent is enabled in front of TomcatService or JettyService, disable it or enforce authorization inside the servlet rather than via path-prefix decorators.
  3. Update JetBrains IDEs, Datalore, and Hub: Update IntelliJ IDEA to >= 2026.3 or >= 2026.2.4, CLion to >= 2026.3 or >= 2026.2.4.1, WebStorm to >= 2026.3 or >= 2026.2.3, Datalore to >= 2026.4, and Hub to >= 2026.2.52556.

Timeline

  • 2026-08-24 to 2026-10-16: Ktor commits 5e938a9b6d9c (constant-time MAC check) and 0aaca706fe5b (KTOR-9477: include IV length and IV in MAC input) land on main and ship in Ktor 3.6.1 on 29-30 October 2026.
  • 2026-11-04 to 2026-11-06 (04:59 UTC): LY Corporation releases Armeria 1.43.0 (e725eb843e7c) and publishes advisories for CVE-2026-11749 and CVE-2026-121819 through CVE-2026-121824.
  • 2026-11-06 (11:17 UTC): JetBrains publishes its November 2026 security bulletin (CVE-2026-123276 through CVE-2026-123327), including CVE-2026-123317 for Ktor < 3.6.1.

From research to remediation

Check whether this pattern exists in your codebase

Turn this research into a remediation workflow. Scan dependencies and package manifests for similar supply-chain risk, then prioritize fixes with reachability context.

References