@siteboon/claude-code-ui ist anfällig für Shell Command Injection in Git Routen

The primary impact of CVE-2026-31861 is the ability for an attacker to execute arbitrary commands on the server hosting the @siteboon/claude-code-ui application. The vulnerability is particularly concerning because JWT authentication can be bypassed, meaning an attacker doesn't necessarily need valid credentials to exploit it. Successful exploitation could lead to data exfiltration, modification of system files, installation of malware, and ultimately, full control of the affected server. The vulnerability’s location within a user configuration endpoint suggests that it could be exploited to gain access to sensitive user data or to modify application behavior.

Organizations using @siteboon/claude-code-ui in their Node.js applications, particularly those relying on JWT authentication for access control, are at risk. Development teams using this package in CI/CD pipelines or automated deployment systems are also vulnerable if they haven't implemented robust input validation. Shared hosting environments where multiple applications share the same server are especially susceptible, as a compromise of one application could lead to the compromise of others.

• nodejs / server:

ps aux | grep '/api/user/git-config' | grep -i 'gitName'| grep -i 'gitEmail'

• nodejs / server:

journalctl -u your-node-app -g 'api/user/git-config' --since "1 hour ago"

• generic web:

curl -I 'your-server.com/api/user/git-config?gitName=;ls' # Check for command execution in response headers

1. 2026-03-10Disclosure

   disclosure

2. 2026-03-10Patch

   patch

1. Reserviert2026-03-09
2. Veröffentlicht2026-03-10
3. Geändert2026-03-13
4. EPSS aktualisiert2026-03-23

The recommended mitigation for CVE-2026-31861 is to immediately upgrade to version 1.24.0 or later of the @siteboon/claude-code-ui package. If upgrading is not immediately feasible, consider implementing input validation and sanitization on the gitName and gitEmail parameters within the /api/user/git-config endpoint to prevent command injection. A Web Application Firewall (WAF) configured to block suspicious shell command patterns could also provide a temporary layer of protection. After upgrading, confirm the fix by attempting to submit a crafted request to the /api/user/git-config endpoint with malicious input and verifying that the command is not executed.