Code execution via build-cache metadata deserialization
Published Jun 26, 2026 · Updated Jun 26, 2026
Unsafe deserialization in JetBrains Kotlin before 2.4.20 allows local users to execute code through crafted build-cache metadata. Kotlin build tooling deserializes build-cache metadata without sufficiently restricting the object data it accepts. Exploitation requires high local privileges and high attack complexity; successful execution runs code in the context of the build process.
Summary
What happened
Unsafe deserialization in JetBrains Kotlin before 2.4.20 allows local users to execute code through crafted build-cache metadata. Kotlin build tooling deserializes build-cache metadata without sufficiently restricting the object data it accepts. Exploitation requires high local privileges and high attack complexity; successful execution runs code in the context of the build process.
The record
- CVE
- CVE-2026-53914
- Published
- Jun 26, 2026
- Updated
- Jun 26, 2026
- Vendor
- JetBrains
- Product
- Kotlin
- Classifications
- CWE-502, T1203
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 26, 2026CVE publishedPublication date reported by the CVE source.
- Jun 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.4.20
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo