CVE-2021-26719
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA directory traversal issue was discovered in Gradle gradle-enterprise-test-distribution-agent before 1.3.2, test-distribution-gradle-plugin before 1.3.2, and gradle-enterprise-maven-extension before 1.8.2. A malicious actor (with certain credentials) can perform a registration step such that crafted TAR archives lead to extraction of files into arbitrary filesystem locations.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA directory traversal vulnerability in Gradle Enterprise test distribution components (agent, gradle-plugin, and maven-extension) allows authenticated users with certain credentials to craft malicious TAR archives during the registration step that extract files to arbitrary filesystem locations outside the intended target directory due to insufficient path validation in TAR extraction logic.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.3.2>= 1.8, <= 1.8.1< 1.3.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Test Distribution Agent versionLocate and inspect the gradle-enterprise-test-distribution-agent installation directory; check the version manifest or build file for the agent version numberAffected if The installed agent version is below 1.3.2
-
Identify Gradle Test Distribution plugin versionInspect the gradle-plugin configuration in your build scripts or Gradle plugins directory; check the test-distribution-gradle-plugin versionAffected if The installed plugin version is below 1.3.2
-
Identify Gradle Maven Extension versionInspect the Maven extension configuration in your .m2 or Gradle caches directory; check the gradle-enterprise-maven-extension versionAffected if The installed Maven extension version is 1.8 through 1.8.1
-
Determine if test distribution is enabledReview your Gradle or Maven configuration files for active test-distribution plugin or extension settings; check for agent registration configurationsAffected if Test distribution features are actively configured and the version is vulnerable
-
Check registration permission configurationReview the access control or authentication settings for test distribution agent registration; identify if untrusted users can register agentsAffected if Registration allows authenticated users with potentially untrusted credentials to complete the registration step
You are affected if any test distribution component (agent, gradle-plugin, or maven-extension) is at a vulnerable version AND test distribution registration is enabled for users who are not fully trusted.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.3.2
Upgrade to gradle-enterprise-test-distribution-agent and test-distribution-gradle-plugin version 1.3.2+ and gradle-enterprise-maven-extension version 1.8.2+ which contain proper path validation; also restrict registration permissions to trusted users only.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26719 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-26719 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data