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.
Published: 2026-05-27
Score: 7.8 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

uniget is a universal tool installer that processes JSON metadata files. Prior to version 0.27.1, the tool command checks the value of the "check" field by invoking /bin/bash -c with the raw string from the metadata. Because this value is taken directly from untrusted JSON without any validation or sanitization, an attacker can craft a metadata file containing malicious shell commands. When users run common uniget operations such as describe, install, update, or inspect, the injected shell code is executed with the privileges of the uniget user, allowing complete compromise of the system.

Affected Systems

The vulnerability affects the uniget command‑line interface distributed by uniget‑org. All releases older than 0.27.1 are affected. The product is referred to as uniget CLI by the vendor.

Risk and Exploitability

The CVSS base score of 7.8 indicates a strong likelihood of exploitation if the vulnerability is present. The EPSS score is not available, so the current exploitation probability cannot be quantified, and the flaw is not listed in the CISA KEV catalog. Attackers can likely exploit the flaw by providing malicious metadata, which may be delivered remotely if the metadata source is untrusted, or locally if an attacker can place a crafted file on the system. The attack path requires execution of uniget commands, so an attacker must be able to run uniget on the target system. Overall, the risk is high for systems that use untrusted metadata sources or run uniget without restricting its input.

Generated by OpenCVE AI on May 27, 2026 at 22:23 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade uniget to version 0.27.1 or later where the check field validation is fixed
  • If upgrade is not immediately possible, restrict the source of metadata files to trusted repositories and avoid processing untrusted JSON content
  • Configure the system to run uniget under a non‑privileged user and enforce access controls to limit the scope of potential code execution

Generated by OpenCVE AI on May 27, 2026 at 22:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-qqq4-5773-pmw5 uniget is Vulnerable to Command Injection in tool.Check Leading to Arbitrary Code Execution
History

Thu, 28 May 2026 13:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Wed, 27 May 2026 21:45:00 +0000

Type Values Removed Values Added
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.
Title uniget: Command Injection in tool.Check Leading to Arbitrary Code Execution
Weaknesses CWE-78
References
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-05-28T12:40:02.534Z

Reserved: 2026-05-08T20:44:38.964Z

Link: CVE-2026-45152

cve-icon Vulnrichment

Updated: 2026-05-28T12:39:52.638Z

cve-icon NVD

Status : Received

Published: 2026-05-27T22:16:36.963

Modified: 2026-05-28T14:16:22.270

Link: CVE-2026-45152

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-05-27T22:30:35Z

Weaknesses