CVE-2026-91164
Received Received - Intake

Authentication Bypass in Warpgate via API Token

Publication date: 2026-09-21

Last updated on: 2026-09-21

Assigner: GitHub, Inc.

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-21
Last Modified
2026-09-21
Generated
2026-09-22
AI Q&A
2026-09-21
EPSS Evaluated
N/A
NVD
CVE-2026-91164
EUVD
EUVD-2026-84062

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
warpgate warpgate to 0.27.3 (inc)
warp-tech warpgate From 0.23.0 (inc) to 0.27.3 (exc)
warp-tech warpgate 0.27.3

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-284 The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Warpgate (versions 0.23.0 to 0.27.2) allows API tokens to bypass IP restrictions. Normally, Warpgate enforces IP allow-lists for interactive logins, but API tokens were not checked against these restrictions. An attacker with a stolen API token could use it from any network location, even if the user's account was configured to only allow access from specific IPs.

Detection Guidance

Check Warpgate logs for API token usage from unexpected IP addresses. Review user accounts with allowed_ip_ranges configured and verify if API tokens were used outside permitted networks. Compare Warpgate version against 0.27.3; versions 0.23.0 to 0.27.2 are vulnerable.

Impact Analysis

If you use Warpgate with IP-restricted accounts, an attacker could exploit this to gain unauthorized access using a leaked API token from any location. This bypasses security controls meant to restrict access to trusted networks. The impact is limited to HTTP API token authentication; other methods like SSH or MySQL are unaffected.

Compliance Impact

This vulnerability could violate compliance requirements that mandate strict access controls and IP restrictions for sensitive data access. Organizations using Warpgate for regulated environments may fail audits if API tokens bypass IP restrictions, potentially exposing data to unauthorized networks.

Mitigation Strategies

Upgrade Warpgate to version 0.27.3 or later. Revoke and reissue API tokens for users with IP restrictions. Restrict network access to the HTTP listener until upgraded. Monitor logs for unauthorized API token usage.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-91164. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart