{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-91166 exists.","fix":"No fix has been published for CVE-2026-91166 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-91166 is a medium-severity vulnerability in warp-tech warpgate, published on 21 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-91166 and fix it if it is affected.\n\nWhat it is: CVE-2026-91166 is a medium-severity vulnerability in warp-tech warpgate, published on 21 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-91166 exists.\n\nAffected product: warp-tech warpgate. 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-91166/ (Markdown: https://insights.sbomify.com/CVE-2026-91166/index.md)","id":"CVE-2026-91166","markdown":"https://insights.sbomify.com/CVE-2026-91166/index.md","name":"CVE-2026-91166","record":{"aliases":["GHSA-w9jj-vpw3-5r8f"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"SSH bastion host","requires_auth":"high_privilege","summary":"Attackers can intercept user traffic and hijack sessions by exploiting improper SSH host key validation in the web interface.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-923","name":"Improper Restriction of Communication Channel to Intended Endpoints"},{"id":"CWE-297","name":"Improper Validation of Certificate with Host Mismatch"}],"description":"Warpgate is an open source SSH, HTTPS and MySQL bastion host for Linux. From 0.25.0 until 0.27.6, the browser SSH path in warpgate-web-ssh/src/manager.rs handles RCEvent::HostKeyUnknown without the presenting hop identity and instead passes ssh_options.host and ssh_options.port for the final target to KnownHosts::trust. In Prompt and AutoAccept modes, a jump host key can therefore be stored for the target address. A machine later presenting the jump host key at the target address can be accepted as the target, allowing interception of user traffic and a newly issued certificate when certificate authentication is used. The native SSH path is unaffected because it tracks each hop separately. This issue is fixed in version 0.27.6.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Warpgate: Web SSH stores a jump host's key against the target's address, so it validates as the target","id":"CVE-2026-91166","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in warpgate","id":"CVE-2026-91167"},"packages":[],"prev":{"headline":"Warpgate: Markup injection in SSO form_post return page via unencoded redirect/error values","id":"CVE-2026-91165"},"products":["warpgate"],"published":"2026-09-21","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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-24","vendors":["warp-tech"]},"summary":"Attackers can intercept user traffic and hijack sessions by exploiting improper SSH host key validation in the web interface.","url":"https://insights.sbomify.com/CVE-2026-91166/"}