Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2021-41589: In Gradle Enterprise before 2021.3 (and Enterprise Build Cache Node before 10.0), there is potential cache poi

60
This week
CRITICAL 9.8REMOTEUPGRADEUPGRADE

CVE-2021-41589 is a critical-severity flaw (CVSS 9.8) affecting build cache node, enterprise. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In Gradle Enterprise before 2021.3 (and Enterprise Build Cache Node before 10.0), there is potential cache poisoning and remote code execution when running the build cache node with its default configuration. This configuration allows anonymous access to the configuration user interface and anonymous write access to the build cache. If access control to the build cache is not changed from the default open configuration, a malicious actor with net

Why this priority

  • Critical severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance2.4% (top 16%)
CISA exploited listNo
WeaknessCWE-732
Published2021-10-27
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: gradle

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

gradle build cache node UPGRADE
Affected: < 10.0
Fixed in: 10.0
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy build-cache-node || rpm -q build-cache-node || build-cache-node --version
2. UPGRADE to 10.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade build-cache-node
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade build-cache-node
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
gradle enterprise UPGRADE
Affected: < 2021.3
Fixed in: 2021.3
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy enterprise || rpm -q enterprise || enterprise --version
2. UPGRADE to 2021.3 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade enterprise
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade enterprise
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2021-41589?

build cache node: upgrade to 10.0; enterprise: upgrade to 2021.3. Exact commands for each OS are on this page.

Is CVE-2021-41589 being exploited?

CVE-2021-41589 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2021-41589 affect?

CVE-2021-41589 affects build cache node, enterprise. Severity is critical (CVSS 9.8). In Gradle Enterprise before 2021.3 (and Enterprise Build Cache Node before 10.0), there is potential cache poisoning and remote code execution when running the build cache node with its default configuration. This configuration allows anony

How urgent is CVE-2021-41589?

Priority 60/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.