CVE-2026-79760: CWE-918: Server-Side Request Forgery (SSRF) in Termix-SSH Termix
Termix versions 2.5.0 up to but not including 2.5.1 contain a server-side request forgery (SSRF) vulnerability. Authenticated users can configure notification channels with attacker-controlled URLs and trigger server-side HTTP requests without destination allowlisting or private address blocking. This allows blind requests to internal services accessible by the Termix server. The vulnerability also permits attacker-controlled HTTP methods and headers in webhook mode, potentially causing limited state changes on internal services. The issue is fixed in version 2.5.1.
AI Analysis
Technical Summary
Termix, a web-based server management platform, has an SSRF vulnerability (CWE-918) in versions >=2.5.0 <2.5.1. Authenticated users can configure webhook or ntfy notification channels with arbitrary destination URLs and trigger server-side requests via a test endpoint. The request path from alert-rules-routes.ts to notification-sender.ts lacks destination allowlisting and private address blocking, enabling blind SSRF to internal HTTP services reachable by the server. Webhook mode allows attacker-controlled HTTP methods and headers, which may cause limited state changes if internal services accept the fixed notification body. Response bodies are not returned. The vulnerability is resolved in version 2.5.1.
Potential Impact
An authenticated attacker can cause the Termix server to make arbitrary HTTP requests to internal services that are otherwise inaccessible externally. This can lead to limited state changes on internal services due to attacker-controlled HTTP methods and headers. There is no confidentiality impact as response bodies are not returned. The vulnerability has a CVSS 3.1 score of 6.4 (medium severity), indicating a moderate risk of integrity and availability impact but no direct confidentiality loss.
Mitigation Recommendations
Upgrade Termix to version 2.5.1 or later, where this SSRF vulnerability is fixed. No other mitigations are specified. Since the vulnerability requires authentication, restricting user access can reduce risk until the upgrade is applied.
CVE-2026-79760: CWE-918: Server-Side Request Forgery (SSRF) in Termix-SSH Termix
Description
Termix versions 2.5.0 up to but not including 2.5.1 contain a server-side request forgery (SSRF) vulnerability. Authenticated users can configure notification channels with attacker-controlled URLs and trigger server-side HTTP requests without destination allowlisting or private address blocking. This allows blind requests to internal services accessible by the Termix server. The vulnerability also permits attacker-controlled HTTP methods and headers in webhook mode, potentially causing limited state changes on internal services. The issue is fixed in version 2.5.1.
CVSS v3.1
Score 6.4medium
Affected software
Termix-SSH
Termix
pkg:github/termix-ssh/TermixRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Termix, a web-based server management platform, has an SSRF vulnerability (CWE-918) in versions >=2.5.0 <2.5.1. Authenticated users can configure webhook or ntfy notification channels with arbitrary destination URLs and trigger server-side requests via a test endpoint. The request path from alert-rules-routes.ts to notification-sender.ts lacks destination allowlisting and private address blocking, enabling blind SSRF to internal HTTP services reachable by the server. Webhook mode allows attacker-controlled HTTP methods and headers, which may cause limited state changes if internal services accept the fixed notification body. Response bodies are not returned. The vulnerability is resolved in version 2.5.1.
Potential Impact
An authenticated attacker can cause the Termix server to make arbitrary HTTP requests to internal services that are otherwise inaccessible externally. This can lead to limited state changes on internal services due to attacker-controlled HTTP methods and headers. There is no confidentiality impact as response bodies are not returned. The vulnerability has a CVSS 3.1 score of 6.4 (medium severity), indicating a moderate risk of integrity and availability impact but no direct confidentiality loss.
Mitigation Recommendations
Upgrade Termix to version 2.5.1 or later, where this SSRF vulnerability is fixed. No other mitigations are specified. Since the vulnerability requires authentication, restricting user access can reduce risk until the upgrade is applied.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-08-25T14:08:18.110Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ab549d5f7a7c54106846f23
Added to database: 09/24/2026, 16:03:33 UTC
Last enriched: 09/24/2026, 16:18:22 UTC
Last updated: 09/24/2026, 16:27:51 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.