CVE-2026-53914 json
JetBrains Kotlin: Unsafe Deserialization in Kotlin Build Cache Enables Code Execution
published 4mo ago modified 17d ago also GHSA-r937-wjx7-w2jp , EUVD-2026-39659
- cvss
- 6.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 29%
- public exploits
- 0
- none known
Summary
In JetBrains Kotlin before 2.4.20 code execution was possible via unsafe deserialization in the build cache metadata
Patch / fix
- maven org.jetbrains.kotlin:kotlin-gradle-plugin 2.4.20-Beta1
- JetBrains Kotlin 2.4.20
Is CVE-2026-53914 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 4mo ago
Exploit prediction
0.35% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.7 | CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 6.7 | CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jetbrains.kotlin:kotlin-gradle-plugin | <2.4.20-Beta1 |
2.4.20-Beta1 |
Affected products
- JetBrains Kotlin
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
github.com
/JetBrains/kotlin/commit/bf51df665b458fda7c3eaf436c4d88dc119d7ec6
web
-
jetbrains.com
/privacy-security/issues-fixed/
vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-53914
advisory
-
github.com
/JetBrains/kotlin
package
-
github.com
/JetBrains/kotlin/releases/tag/v2.4.20-Beta1
web
-
jetbrains.com
/privacy-security/issues-fixed
web
Sources
- CVE List CVE-2026-53914
- GitHub Advisory GHSA-r937-wjx7-w2jp
- NVD CVE-2026-53914
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.