CVE-2021-41588 Deserialization in n/a
An attacker with encryption and signing keys can trigger unsafe Java object deserialization in Gradle Enterprise, potentially leading to code execution.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2021-41588?
CVE-2021-41588 is a high-severity unsafe deserialization vulnerability in n/a, published on 24 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
In Gradle Enterprise before 2021.1.3, a crafted request can trigger deserialization of arbitrary unsafe Java objects. The attacker must have the encryption and signing keys.
Weakness: CWE-502
Which versions are affected by CVE-2021-41588?
1 open source package ship an affected version, including gradle. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gradle Bitnami | From 2017.2.0 | 2021.1.3 |
Products include Gradle Gradle.
How do I fix CVE-2021-41588?
Upgrade gradle to 2021.1.3 or later.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2021-41588 being exploited?
There is no known exploitation of CVE-2021-41588 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-2019-15052 Information disclosure in n/a
- CVE-2016-6199 Deserialization in n/a
- CVE-2021-29428 Local privilege escalation through system temporary directory
- CVE-2026-22816 Gradle fails to disable repositories which can expose builds to malicious artifacts
- CVE-2026-22865 Gradle's failure to disable repositories failing to answer can expose builds to malicious artifacts
Sources
Also known as BIT-gradle-2021-41588, GHSA-2j29-824j-4f3v.