# CVE-2026-45152: uniget: Command Injection in tool.Check Leading to Arbitrary Code Execution

> Attackers can execute arbitrary shell commands via malicious metadata in uniget, leading to code execution with user privileges.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-qqq4-5773-pmw5, GO-2026-5590

## What is CVE-2026-45152?

CVE-2026-45152 is a high-severity command injection vulnerability in uniget-org cli, published on 27 May 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.

### Official description

uniget is a universal installer and updater for (container) tools. Prior to 0.27.1, a command injection vulnerability exists in uniget due to unsafe execution of the check field from metadata files using /bin/bash -c. Because the check field is loaded directly from untrusted JSON metadata without validation or sanitization, an attacker can craft malicious metadata that executes arbitrary shell commands on the victim’s system when common uniget operations such as describe, install, update, or inspect are performed. This vulnerability can lead to arbitrary code execution with the privileges of the user running uniget. This vulnerability is fixed in 0.27.1.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-45152?

3 open source packages ship an affected version, including gitlab.com/uniget-org/cli.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gitlab.com/uniget-org/cli` | Go | All versions | 0.27.1 |
| `gitlab.com/uniget-org/cli` | Go | All versions | 0.27.1 |
| `gitlab.com/uniget-org/cli` | Go | All versions | 0.27.1 |

## How do I fix CVE-2026-45152?

Upgrade gitlab.com/uniget-org/cli to 0.27.1 or later.

## Is CVE-2026-45152 being exploited?

There is no known exploitation of CVE-2026-45152 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45152 and fix it if it is affected.

What it is: CVE-2026-45152 is a high-severity command injection vulnerability in uniget-org cli, published on 27 May 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.
Exploitation: There is no known exploitation of CVE-2026-45152 in the wild and no public exploit code.

Affected packages and fixed versions:
- gitlab.com/uniget-org/cli (Go): affected all versions; fixed in 0.27.1
- gitlab.com/uniget-org/cli (Go): affected all versions; fixed in 0.27.1
- gitlab.com/uniget-org/cli (Go): affected all versions; fixed in 0.27.1

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45152/ (Markdown: https://insights.sbomify.com/CVE-2026-45152/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45152
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45152
- OSV: https://osv.dev/vulnerability/CVE-2026-45152

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45152/
Summaries are generated and may contain mistakes; the official description above is the record.