OS Command Injection in gitlab.com/uniget-org/cli (CVE-2026-45152)
Summary
OS command injection in gitlab.com/uniget-org/cli (CVE-2026-45152). Successful exploitation can lead to full system takeover. Exploitable via check. Mitigation: upgrade to 0.27.1 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45152 has been found in gitlab.com/uniget-org/cli.
Attackers can target a specific entry point like check over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade gitlab.com/uniget-org/cli to 0.27.1 or later.
If unsure, ask your IT team or search "gitlab.com/uniget-org/cli CVE-2026-45152" on the vendor's site.
CVE-2026-45152 (gitlab.com/uniget-org/cli) — CWE-78 / CVSS v3 7.8
Attack vector: local / unauthenticated
Attack surface: check / describe / install / update
Patched: 0.27.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
OS command injection (CWE-78) exists in gitlab.com/uniget-org/cli. Attackers reach the vulnerable code path via check without authentication.
Check the vendor advisory for the affected versions of gitlab.com/uniget-org/cli. Attack surface: check / describe / install / update.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
Update to 0.27.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'gitlab.com/uniget-org/cli' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'gitlab.com/uniget-org/cli' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
gitlab.com/uniget-org/cliを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade gitlab.com/uniget-org/cli to 0.27.1ステージング環境で 0.27.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com