CVE-2026-79761 json
Termix: Command injection in SSH key deployment verification
published 2026-09-24 46 d ago modified 2026-10-05 35 d ago also EUVD-2026-86158
- cvss
- 6.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 29%
- public exploits
- 0
- none known
Summary
Termix is a web-based server management platform with SSH terminal, tunneling, and file editing capabilities. From 1.7.0 until 2.5.1, the Termix SSH key deployment flow derives a grep pattern from a user-controlled public-key token and interpolates it into double-quoted shell commands executed on the selected target host. In src/backend/database/routes/credential-deploy-routes.ts, both grep -F verification paths accept command substitution or quote-breaking shell syntax in keyPattern. An authenticated user who can deploy a crafted SSH credential can therefore execute commands with the selected remote account's privileges. The separate ACME command-injection report is outside this CVE's scope. This issue is fixed in version 2.5.1.
Patch / fix
- termix termix 2.5.1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 35 d ago
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.6 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L |
Affected products
- Termix-SSH Termix
Classification
- Weakness
-
- CWE-78 Improper Neutralization of Special Elements used in an OS Command
References
- github.com /Termix-SSH/Termix/pull/1067
- github.com /Termix-SSH/Termix/commit/ddbdd5c437c2296607dfaa4265d6f63fbc1ca92e
- github.com /Termix-SSH/Termix/commit/fafff94e5e31c3843df06aa08773bbaa879bbede
- github.com /Termix-SSH/Termix/security/advisories/GHSA-p2g3-2xq3-23gx
- github.com /Termix-SSH/Termix/releases/tag/release-2.5.1-tag
Sources
- CVE List CVE-2026-79761
- NVD CVE-2026-79761
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.