Unsafe Deserialization in org.jetbrains.kotlin:kotlin-gradle-plugin (CVE-2026-53914)
Summary
Vulnerability in org.jetbrains.kotlin:kotlin-gradle-plugin (CVE-2026-53914). Confidential information can be exposed externally. Mitigation: upgrade to 2.4.20-Beta1 or later.
Original description
The description as published by the source.
In JetBrains Kotlin before 2.4.20 code execution was possible via unsafe deserialization in the build cache metadata
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-53914 has been found in org.jetbrains.kotlin:kotlin-gradle-plugin.
Confidential information can be exposed externally. CVSS score: 6.7/10.
What to do: upgrade org.jetbrains.kotlin:kotlin-gradle-plugin to 2.4.20-Beta1 or later.
If unsure, ask your IT team or search "org.jetbrains.kotlin:kotlin-gradle-plugin CVE-2026-53914" on the vendor's site.
CVE-2026-53914 (org.jetbrains.kotlin:kotlin-gradle-plugin) — CWE-502 / CVSS v3 6.7
Attack vector: local / no user interaction
Patched: 2.4.20-Beta1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Unsafe deserialization (CWE-502) exists in org.jetbrains.kotlin:kotlin-gradle-plugin.
Check the vendor advisory for the affected versions of org.jetbrains.kotlin:kotlin-gradle-plugin.
Severity: Medium (CVSS 6.7/10). Confidential information can be exposed externally.
Update to 2.4.20-Beta1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.jetbrains.kotlin:kotlin-gradle-plugin を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.jetbrains.kotlin:kotlin-gradle-plugin to 2.4.20-Beta1ステージング環境で 2.4.20-Beta1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- patch cve@jetbrains.com
- web github.com
- web nvd.nist.gov
- web jetbrains.com
- web github.com
- web github.com