CVE-2021-29427

What it is

In Gradle from version 5.1 and before version 7.0 there is a vulnerability which can lead to information disclosure and/or dependency poisoning. Repository content filtering is a security control Gradle introduced to help users specify what repositories are used to resolve specific dependencies. This feature was introduced in the wake of the "A Confusing Dependency" blog post. In some cases, Gradle may ignore content filters and search all repositories for dependencies. This only occurs when repository content filtering is used from within a `pluginManagement` block in a settings file. This may change how dependencies are resolved for Gradle plugins and build scripts. For builds that are vulnerable, there are two risks: 1) Information disclosure: Gradle could make dependency requests to repositories outside your organization and leak internal package identifiers. 2) Dependency poisoning/Dependency confusion: Gradle could download a malicious binary from a repository outside your organization due to name squatting. For a full example and more details refer to the referenced GitHub Security Advisory. The problem has been patched and released with Gradle 7.0. Users relying on this feature should upgrade their build as soon as possible. As a workaround, users may use a company repository which has the right rules for fetching packages from public repositories, or use project level repository content filtering, inside `buildscript.repositories`. This option is available since Gradle 5.1 when the feature was introduced.

At a glance

Exploitability

Can be exploited over the network with an admin-level account. High risk of data exposure, data tampering, service disruption.

Exploit odds

1.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2021-04-13 20:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 03:47 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.3% in the next 30 days (EPSS).
• Severity: 8.0 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2021-04-13 20:15 UTC

Last modified

2026-06-17 03:47 UTC

Exploit probability

1.3% · EPSS, next 30 days

Weakness

CWE-829

Record status

Modified

Affected

• Gradle < 7.0
• Quarkus ≤ 2.2.3

Attack profile CVSS 3.1 · 8.0

Attack vector

Network

Complexity

High

Privileges needed

High

User interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2021-29427.md and follow it. Check whether this project is affected by CVE-2021-29427. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge