CVE-2026-91163 is a vulnerability in warpgate, an open source bastion host, affecting versions prior to 0.29.0. It allows unauthenticated network clients to trigger error messages containing sensitive internal diagnostic information due to improper error handling in the Kubernetes protocol listener. This information disclosure does not include user data and does not impact integrity or availability. The issue is fixed in version 0.29.0.
CVE-2026-91168 is an authorization bypass vulnerability in warpgate versions 0.21.0 through 0.28.0. The flaw arises because the Kubernetes request correlator uses mutable identifiers (username, target_name, client IP) instead of immutable user UUIDs to key authorized targets. This allows a low-privilege account that reuses a deleted username to inherit the predecessor's live authorization entry, bypassing fresh authorization checks and potentially accessing or mutating Kubernetes cluster resources without proper permission. The issue is fixed in warpgate version 0.29.0.
CVE-2026-91167 is a missing authorization vulnerability in warp-tech's warpgate before version 0.28.4. It allows a limited administrator with any permission to update expiration and revocation timestamps on existing user role assignments without requiring the proper AccessRolesAssign permission. This can extend or reinstate role grants but cannot create new role assignments. The issue is fixed in version 0.28.4.
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.
Warpgate is an open source SSH, HTTPS and MySQL bastion host for Linux. Prior to 0.27.6, the response_mode=form_post SSO return path in warpgate-protocol-http/src/api/sso_provider_list.rs uses serde_json::to_string inside ReturnToSsoPostResponse without neutralizing a script-closing sequence. The vulnerable value can enter the script block through the attacker-controlled next redirect parameter stored by warpgate-protocol-http/src/api/sso_provider_detail.rs or through IdP-derived error messages that make_redirect_url concatenates without URL encoding. The IdP-derived path is reachable when the attacker controls a configured identity provider, or when the attacker controls the email or username claim on an attacker-controlled account and the configured identity provider permits the required unvalidated claim format. A victim must complete the form_post SSO flow for the injected markup to be rendered. The Warpgate Content-Security-Policy blocks injected JavaScript and event handlers, so the demonstrated impact is content spoofing, a false login form, or a meta refresh rather than script execution. This issue is fixed in version 0.27.6.
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.
Warpgate is an open source SSH, HTTPS and MySQL bastion host for Linux. Prior to 0.25.6, api_get_recording_stream in warpgate-admin/src/api/recordings_detail.rs protects /@warpgate/admin/api/recordings/{uuid}/stream only with session authentication and omits require_admin_permission for AdminPermission::RecordingsView. Any authenticated regular user who identifies an active recording can subscribe to its WebSocket and receive real-time terminal input and output from proxied SSH, MySQL, or PostgreSQL sessions, including credentials, commands, and other sensitive data belonging to users and administrators. This issue is fixed in version 0.25.6.
CVE-2026-63329 is a medium severity vulnerability in warp-tech warpgate, an open source SSH, HTTPS, and MySQL bastion host for Linux. Versions prior to 0.25.6 improperly forward client-supplied x-warpgate-username headers, allowing an authenticated attacker to potentially impersonate another user if the backend trusts the first header value. The vulnerability also involves acceptance of the reserved x-warpgate-authentication-type header without exclusion. This issue is fixed in version 0.25.6.
CVE-2026-58491 is a critical cross-site scripting (XSS) vulnerability in the open source bastion host Warpgate prior to version 0.25.5. The vulnerability arises from improper neutralization of an attacker-controlled 'next' parameter in the SSO API endpoints, which is inserted into HTTP responses without HTML escaping. This allows an attacker to execute arbitrary JavaScript in the context of an authenticated user's browser, potentially exposing session data and enabling unauthorized actions via user and administrator APIs. Additionally, the same parameter can be used for open redirect attacks. The issue is fixed in Warpgate version 0.25.5.
Warpgate is an open source SSH, HTTPS and MySQL bastion host for Linux. Prior to 0.23.3, the SSO flow does not validate the state parameter, which makes it possible for an attacker to trick a user into logging into the attacker's account, possibly convincing them to perform sensitive actions on the attacker's account (such as writing sensitive data to the attacker's SSH target, or logging into an HTTP target that the attacker set up). This vulnerability is fixed in 0.23.3.