{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-79760 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-79760 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-79760 is a medium-severity server-side request forgery vulnerability in Termix-SSH Termix, published on 24 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-79760 and fix it if it is affected.\n\nWhat it is: CVE-2026-79760 is a medium-severity server-side request forgery vulnerability in Termix-SSH Termix, published on 24 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-79760 in the wild and no public exploit code.\n\nAffected product: Termix-SSH Termix. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-79760/ (Markdown: https://insights.sbomify.com/CVE-2026-79760/index.md)","id":"CVE-2026-79760","markdown":"https://insights.sbomify.com/CVE-2026-79760/index.md","name":"CVE-2026-79760","record":{"aliases":["GHSA-6hx3-9mgq-h9fj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Termix server management","requires_auth":"low_privilege","summary":"Authenticated users can trigger blind SSRF via notification test endpoints, allowing access to internal services and limited state changes.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Termix: Authenticated blind SSRF through notification channel test endpoints","id":"CVE-2026-79760","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Termix: Command injection in SSH key deployment verification","id":"CVE-2026-79761"},"packages":[],"prev":{"headline":"Termix: Cross-User Information Disclosure via Missing Ownership Check in deploy-to-host Endpoint","id":"CVE-2026-79759"},"products":["Termix"],"published":"2026-09-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-28","vendors":["Termix-SSH"]},"summary":"Authenticated users can trigger blind SSRF via notification test endpoints, allowing access to internal services and limited state changes.","url":"https://insights.sbomify.com/CVE-2026-79760/"}