CVE-2026-79760: Termix: Authenticated blind SSRF through notification channel test endpoints
Termix is a web-based server management platform with SSH terminal, tunneling, and file editing capabilities. From 2.5.0 until 2.5.1, Termix allows authenticated users to configure webhook or ntfy notification channels with attacker-controlled destination URLs and trigger server-side requests through the notification-channel test endpoint. The request path in src/backend/database/routes/alert-rules-routes.ts reaches src/backend/utils/notification-sender.ts without destination allowlisting or private-address blocking. This permits blind requests to internal HTTP services reachable by the Termix server. Webhook mode also permits attacker-controlled HTTP methods and headers, which can cause limited state changes when an internal service accepts the fixed notification body, although response bodies are not returned. This issue is fixed in version 2.5.1.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Termixto a version that resolves this vulnerability.Fixed in 2.5.1
Event History
Frequently Asked Questions
Who can exploit this issue?
An authenticated Termix user can exploit it by configuring a webhook or ntfy notification channel with a chosen destination URL and invoking the notification-channel test endpoint. The affected request can reach internal HTTP services that are network-accessible from the Termix server.
What can an attacker do through the vulnerable notification channel?
The issue enables blind server-side requests, so response bodies are not returned to the attacker. In webhook mode, an attacker can also control HTTP methods and headers, potentially causing limited state changes on internal services that accept the fixed notification body.
Which versions need remediation?
Termix versions from 2.5.0 until 2.5.1 are affected. Upgrade to version 2.5.1, which fixes the issue.