---
id: CVE-2026-91164
title: 'Warpgate is an open source SSH, HTTPS and MySQL bastion host for Linux'
summary: >-
  Warpgate is an open source SSH, HTTPS and MySQL bastion host for Linux. From
  0.23.0 until 0.27.3, HTTP API token authentication resolves
  ConfigProvider::validate_api_token into RequestAuthorization::UserToken
  without enforcing the owning…
severity: medium
cvss: 4.3
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'
cwe:
  - CWE-284
  - CWE-863
vendor: warp-tech
product: warpgate
affected:
  - 'warpgate >= 0.23.0, < 0.27.3'
published: '2026-09-21'
updated: '2026-09-24'
sourceUpdated: '2026-09-24T21:25:27.050'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-91164'
references:
  - url: >-
      https://github.com/warp-tech/warpgate/commit/8cb33a1a7c447ab0cde3a1ee9f95bf9dde905482
    label: security-advisories@github.com
  - url: 'https://github.com/warp-tech/warpgate/pull/2356'
    label: security-advisories@github.com
  - url: 'https://github.com/warp-tech/warpgate/releases/tag/v0.27.3'
    label: security-advisories@github.com
  - url: >-
      https://github.com/warp-tech/warpgate/security/advisories/GHSA-qmr2-wp96-h9ff
    label: security-advisories@github.com
tags:
  - nvd
  - cve.org
epss: 0.00421
epssPercentile: 0.33726
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-09-21T19:06:54.705180Z'
ingestedAt: '2026-09-21T19:51:58.863Z'
---

## Overview

Warpgate is an open source SSH, HTTPS and MySQL bastion host for Linux. From 0.23.0 until 0.27.3, HTTP API token authentication resolves ConfigProvider::validate_api_token into RequestAuthorization::UserToken without enforcing the owning user's allowed_ip_ranges against the trusted client address in warpgate-protocol-http/src/common.rs. An attacker holding a leaked, phished, or exfiltrated X-Warpgate-Token can therefore use it from a prohibited network location. Deployments without allowed_ip_ranges are unaffected, and HTTP target proxying plus SSH, MySQL, PostgreSQL, RDP, VNC, and Kubernetes paths do not accept this vulnerable HTTP token flow. This issue is fixed in version 0.27.3.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.