{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-79763 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-79763 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-79763 is a medium-severity authentication bypass 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-79763 and fix it if it is affected.\n\nWhat it is: CVE-2026-79763 is a medium-severity authentication bypass 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-79763 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-79763/ (Markdown: https://insights.sbomify.com/CVE-2026-79763/index.md)","id":"CVE-2026-79763","markdown":"https://insights.sbomify.com/CVE-2026-79763/index.md","name":"CVE-2026-79763","record":{"aliases":["GHSA-x9h9-f7jc-8jwj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Server management platform","requires_auth":"low_privilege","summary":"Attackers with session and password can disable MFA or reset backup codes, bypassing two-factor authentication in Termix.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-308","name":"Use of Single-factor Authentication"}],"description":"Termix is a web-based server management platform with SSH terminal, tunneling, and file editing capabilities. From 2.4.0 until 2.5.1, the POST /users/totp/disable and POST /users/totp/backup-codes endpoints accept the account password as the sole reauthentication factor after a 2.4.0 refactor regressed the two-factor check introduced for CVE-2026-45749. In src/backend/database/routes/user-totp-routes.ts, verifyTotpReauth returns success when bcrypt.compare validates the password, while each endpoint chooses password or totp_code as an interchangeable credential. An attacker who has a victim's authenticated session and knows the password can disable TOTP or regenerate and invalidate backup codes without an authenticator or valid second factor, weakening the account to single-factor authentication. 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: MFA-critical operations accept the account password as a sole factor (regression of CVE-2026-45749)","id":"CVE-2026-79763","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Termix: Authenticated SSRF via `/homepage/proxy` — No Destination Allowlist","id":"CVE-2026-79764"},"packages":[],"prev":{"headline":"Hardcoded credentials in Termix","id":"CVE-2026-79762"},"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-24","vendors":["Termix-SSH"]},"summary":"Attackers with session and password can disable MFA or reset backup codes, bypassing two-factor authentication in Termix.","url":"https://insights.sbomify.com/CVE-2026-79763/"}