LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25063: gradle-completion has a Bash command injection issue

gradle-completion provides Bash and Zsh completion support for Gradle. A command injection vulnerability was found in gradle-completion up to and including 9.3.0 that allows arbitrary code execution when a user triggers Bash tab completion in a project containing a malicious Gradle build file. The `gradle-completion` script for Bash fails to adequately sanitize Gradle task names and task descriptions, allowing command injection via a malicious Gradle build file when the user completes a command in Bash (without them explicitly running any task in the build). For example, given a task description that includes a string between backticks, then that string would be evaluated as a command when presenting the task description in the completion list. While task execution is the core feature of Gradle, this inherent execution may lead to unexpected outcomes. The vulnerability does not affect zsh completion. The first patched version is 9.3.1. As a workaround, it is possible and effective to temporarily disable bash completion for Gradle by removing `gradle-completion` from `.bashrc` or `.bash_profile`.

HighCVSS 8.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-25063 affects gradle-completion for Bash. A malicious Gradle project can cause commands to run when a developer merely uses tab completion, before running any Gradle task. This mainly threatens developer workstations that install Bash completion and open untrusted or compromised Gradle projects.

Executive priority

Prioritize remediation for developer endpoints handling third-party code. This is not a typical internet-exposed server issue, but it can compromise workstations through routine developer behavior. Treat as high priority for engineering environments and code-review workflows.

Technical view

gradle-completion before 9.3.1 insufficiently sanitizes Gradle task names and descriptions used by Bash completion output. Crafted build metadata can trigger command injection during completion rendering. The advisory states Zsh completion is not affected. CVSS v4.0 is 8.3 high, with local attack vector and active user interaction required.

Likely exposure

Exposure is most likely on Linux or macOS developer systems using Bash with gradle-completion loaded. Risk rises for teams cloning external Gradle repositories or reviewing untrusted pull requests. Systems using Zsh completion are not affected according to the advisory.

Exploitation context

No active exploitation is stated in the provided sources, and the CVE is not marked KEV. Exploitation requires a malicious Gradle build file and a user triggering Bash tab completion in that project. It does not require the user to explicitly execute a Gradle task.

Researcher notes

The root issue is Bash completion rendering unsanitized Gradle task names or descriptions. Sources identify CWE-78 and CWE-157. Public sources provide a patch commit and vendor advisory, but no evidence of exploitation in the wild was provided.

Mitigation direction

  • Upgrade gradle-completion to version 9.3.1 or later.
  • Temporarily remove gradle-completion from .bashrc or .bash_profile.
  • Warn developers not to use Bash completion in untrusted Gradle projects.
  • Check vendor guidance for any environment-specific updates.

Validation and detection

  • Inventory developer machines for gradle-completion versions below 9.3.1.
  • Review Bash startup files for gradle-completion loading.
  • Confirm affected users use Bash, not only Zsh completion.
  • Verify upgraded systems report gradle-completion 9.3.1 or later.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-157: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · medium confidence lookup

CWE-78: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-25063 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.3 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:A/VC:H/VI:H/VA:H/SC:N/SI:H/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.3CVSS 4.0HighCVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:A/VC:H/VI:H/VA:H/SC:N/SI:H/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.3High
CVSS 4.0 vector shape for CVE-2026-25063Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:A/VC:H/VI:H/VA:H/SC:N/SI:H/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
gradlegradle-completion< 9.3.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-157 · source CWE mapping

Failure to Sanitize Paired Delimiters

Failure to Sanitize Paired Delimiters represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-78 · source CWE mapping

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.