Is this vulnerability remotely exploitable?

It is not directly exploitable over the network, but it becomes exploitable when a developer opens and uses Bash completion in a project whose Gradle build files have been crafted by an attacker, such as a cloned repository or shared template.

What level of access does an attacker need?

An attacker needs the ability to influence the Gradle build files in a project that a developer will work with while Bash completion is enabled. This can happen through supplying a malicious repository, example project, or patch that introduces dangerous task names or descriptions.

What is the safest general fix pattern?

The safest pattern is to ensure that any data coming from build files (task names, descriptions, or other metadata) is treated as untrusted and is properly escaped before being used in shell contexts, and to avoid command substitutions or `eval` on such data in completion scripts.

Severity:

HIGH RISK

(7.8)

Command Injection in Bash Completion (CWE-78) for gradle-completion

CVE-2026-25063

Published:

Jan 29, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

Command Injection

CWE:

CWE-78;CWE-157

Impact:

Arbitrary Command Execution on Developer Workstations

Severity:

HIGH RISK

(7.8)

CVSS Version:

3.1

Vulnerability Type

Category:

Command Injection

CWE:

CWE-78;CWE-157

Impact:

Arbitrary Command Execution on Developer Workstations

Severity:

HIGH RISK

(7.8)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Command Injection in Bash Completion (CWE-78) for gradle-completion

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal