Code execution via unsanitized Bash completion descriptions
Published Jan 29, 2026 · Updated Jan 29, 2026
Command injection in Gradle, Inc. gradle-completion 9.3.0 and earlier allows local users to execute code through Bash tab completion. The Bash script places untrusted task names and descriptions from Gradle output into array-building command substitutions, causing backtick-delimited text to be evaluated by the shell. Execution requires a user to enter an attacker-controlled project and invoke Bash completion; Zsh completion is not affected.
Summary
What happened
Command injection in Gradle, Inc. gradle-completion 9.3.0 and earlier allows local users to execute code through Bash tab completion. The Bash script places untrusted task names and descriptions from Gradle output into array-building command substitutions, causing backtick-delimited text to be evaluated by the shell. Execution requires a user to enter an attacker-controlled project and invoke Bash completion; Zsh completion is not affected.
The record
- CVE
- CVE-2026-25063
- Published
- Jan 29, 2026
- Updated
- Jan 29, 2026
- Vendor
- Gradle, Inc.
- Product
- gradle-completion
- Classifications
- CWE-157, CWE-78, T1059.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 29, 2026CVE publishedPublication date reported by the CVE source.
- Jan 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 9.3.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo