OS Command Injection in Termix (CVE-2026-79766)
Summary
OS command injection in Termix (CVE-2026-79766). Successful exploitation can lead to full system takeover. Exploitable via PATCH /users/acme-ssl-settings.
Original description
The description as published by the source.
Termix is a web-based server management platform with SSH terminal, tunneling, and file editing capabilities. From 2.4.1 until 2.5.1, an authenticated Termix administrator can store attacker-controlled domain and email values through PATCH /users/acme-ssl-settings and trigger their interpolation into a certbot shell command through POST /users/acme-ssl-request. In src/backend/database/routes/acme-ssl-routes.ts, child_process.execSync invokes /bin/sh -c with those values only wrapped in double quotes, so shell metacharacters can execute arbitrary operating-system commands as the Termix backend process. Both HTTP webroot and DNS Cloudflare challenge modes are affected, and compromise exposes Termix databases, process secrets, stored credentials, and network reachability. This issue is fixed in version 2.5.1.
Source: NIST National Vulnerability Database NVD
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-79766 has been found in Termix.
Attackers can target a specific entry point like PATCH /users/acme-ssl-settings over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Termix CVE-2026-79766" on the vendor's site.
CVE-2026-79766 (Termix) — CWE-78 / CVSS v3 9.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PATCH /users/acme-ssl-settings / POST /users/acme-ssl-request.
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 Termix. Attackers reach the vulnerable code path via PATCH /users/acme-ssl-settings.
Check the vendor advisory for the affected versions of Termix. Attack surface: PATCH /users/acme-ssl-settings / POST /users/acme-ssl-request..
Severity: Critical (CVSS 9.1/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual PATCH /users/acme-ssl-settings requests with malformed payloads or SQL meta-characters. Run grep -r 'Termix' . 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 'Termix' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Termixを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'PATCH /users/acme-ssl-settings' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PATCH /users/acme-ssl-settingsへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against PATCH /users/acme-ssl-settings on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。