Is CVE-2026-45152 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-45152 being exploited in the wild.

How severe is CVE-2026-45152?

High severity, with a CVSS score of 7.8, published 27 May 2026.

Which products and versions are affected?

gitlab.com/uniget-org/cli (Go) < 0.27.1, SEMVER:introduced=0,fixed=0.27.1; Uniget-Org Uniget <= 0.27.0.

Is there a fix for CVE-2026-45152?

Yes. gitlab.com/uniget-org/cli (Go): upgrade to 0.27.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-45152 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-45152?

Check whether you run gitlab.com/uniget-org/cli (Go) or Uniget-Org Uniget at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-45152: uniget command injection in metadata check field

Q: Is there a fix for CVE-2026-45152?

Yes. gitlab.com/uniget-org/cli (Go): upgrade to 0.27.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-45152 attacked?

It is attacked with local access, in a software library.

Q: Am I affected by CVE-2026-45152?

Check whether you run gitlab.com/uniget-org/cli (Go) or Uniget-Org Uniget at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-45152 · Severity: high · CVSS 7.8 · Published 2026-05-27

uniget is a command-line tool used for managing and installing other software tools. A security flaw allows an attacker to execute malicious commands on a user's computer if the user processes a specially crafted metadata file. This could lead to full system compromise, data theft, or the installation of malware with the same permissions as the user running the tool.

Technologies: gitlab.com/uniget-org/cli (Go). Vendors: Go.

Quick answers

Is CVE-2026-45152 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-45152 being exploited in the wild.
How severe is CVE-2026-45152?: High severity, with a CVSS score of 7.8, published 27 May 2026.
Which products and versions are affected?: gitlab.com/uniget-org/cli (Go) < 0.27.1, SEMVER:introduced=0,fixed=0.27.1; Uniget-Org Uniget <= 0.27.0.
Is there a fix for CVE-2026-45152?: Yes. gitlab.com/uniget-org/cli (Go): upgrade to 0.27.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-45152 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-45152?: Check whether you run gitlab.com/uniget-org/cli (Go) or Uniget-Org Uniget at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

gitlab.com/uniget-org/cli (Go): upgrade to 0.27.1 or later
```
go get gitlab.com/uniget-org/cli@v0.27.1
```

Technical details

A command injection vulnerability exists in uniget's metadata processing logic. The application uses `json.Unmarshal()` to populate a `Tool` struct from JSON metadata files and subsequently executes the content of the `Check` field using `/bin/bash -c` within the `RunVersionCheck` function. Because this field is not validated or sanitized, an attacker can inject shell metacharacters (e.g., `;`, `&&`, `|`) into the metadata. Exploitation occurs when a user performs common operations like `describe`, `install`, or `update` on a tool associated with the malicious metadata. This issue is patched in version 0.27.1.

Affected products

uniget-org cli < 0.27.1

Identifiers

CVE-2026-45152
GHSA-qqq4-5773-pmw5
GO-2026-5590

Timeline

2026-05-08: disclosed
2026-05-13: advisory
2026-05-13: patched: Version 0.27.1 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.