{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-25063 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-25063 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-25063 is a high-severity command injection vulnerability in gradle-completion, published on 29 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-25063 and fix it if it is affected.\n\nWhat it is: CVE-2026-25063 is a high-severity command injection vulnerability in gradle-completion, published on 29 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-25063 in the wild and no public exploit code.\n\nAffected product: gradle-completion. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-25063/ (Markdown: https://insights.sbomify.com/CVE-2026-25063/index.md)","id":"CVE-2026-25063","markdown":"https://insights.sbomify.com/CVE-2026-25063/index.md","name":"CVE-2026-25063","record":{"aliases":["DEBIAN-CVE-2026-25063","GHSA-qggc-44r3-cjgv","UBUNTU-CVE-2026-25063"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Gradle Bash completion","requires_auth":"high_privilege","summary":"Attackers can execute arbitrary code via malicious Gradle build files when users trigger Bash tab completion, requiring an upgrade to gradle-completion.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"gradle-completion","vendor":"gradle"}],"cvss":{"score":8.3,"severity":"high","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"},{"id":"CWE-157","name":"Failure to Sanitize Paired Delimiters"}],"description":"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`.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"gradle-completion has a Bash command injection issue","id":"CVE-2026-25063","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"SmarterTools SmarterMail \u003c Build 9518 Unauthenticated background-of-the-day Path Coercion","id":"CVE-2026-25067"},"packages":[],"prev":{"headline":"Outline Affected an Arbitrary File Read via Path Traversal in JSON Import","id":"CVE-2026-25062"},"products":["gradle-completion"],"published":"2026-01-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-10","vendors":["gradle"]},"summary":"Attackers can execute arbitrary code via malicious Gradle build files when users trigger Bash tab completion, requiring an upgrade to gradle-completion.","url":"https://insights.sbomify.com/CVE-2026-25063/"}