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 .bashprofile.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-25063?
CVE-2026-25063 is classified as a high-severity command injection vulnerability.
How do I fix CVE-2026-25063?
Upgrade gradle-completion to version 9.4.0 or later to mitigate the vulnerability.
What impact does CVE-2026-25063 have on my system?
CVE-2026-25063 allows an attacker to execute arbitrary code on the system through malicious Gradle build files.
Who is affected by CVE-2026-25063?
All users of gradle-completion versions 9.3.0 and earlier are potentially affected by CVE-2026-25063.
When was CVE-2026-25063 disclosed?
CVE-2026-25063 was disclosed as part of ongoing security assessments of the gradle-completion tool.