JetBrains Ktor

• CVE-2026-68762 Medium 5.9 In JetBrains Ktor before 3.4.1 potential DoS attack via WebSocket decompression was possible 0.4%
• CVE-2025-29904 Medium 5.3 In JetBrains Ktor before 3.1.1 an HTTP Request Smuggling was possible 0.3%
• CVE-2024-49580 Medium 5.3 In JetBrains Ktor before 2.3.13 improper caching in HttpCache Plugin could lead to response information disclosure 0.4%
• CVE-2023-45613 Medium 6.8 In JetBrains Ktor before 2.3.5 server certificates were not verified 0.4%
• CVE-2023-45612 High 8.6 In JetBrains Ktor before 2.3.5 default configuration of ContentNegotiation with XML format was vulnerable to XXE 0.7%
• CVE-2023-34339 Low 3.3 In JetBrains Ktor before 2.3.1 headers containing authentication data could be added to the exception's message 0.2%
• CVE-2022-48476 High 7.5 In JetBrains Ktor before 2.3.0 path traversal in the `resolveResource` method was possible 0.8%
• CVE-2022-38180 Medium 5.3 In JetBrains Ktor before 2.1.0 the wrong authentication provider could be selected in some cases 0.8%
• CVE-2022-38179 Medium 4.7 JetBrains Ktor before 2.1.0 was vulnerable to the Reflect File Download attack 0.5%
• CVE-2022-29930 High 8.7 SHA1 implementation in JetBrains Ktor Native 2.0.0 was returning the same value. The issue was fixed in Ktor version 2.0.1. 0.9%
• CVE-2022-29035 Low 3.3 In JetBrains Ktor Native before version 2.0.0 random values used for nonce generation weren't using SecureRandom implementations 0.6%