Skip to main content
← Vulnerabilities

Warpgate: Kubernetes authorization correlation can be reused by a recreated same-name account

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

6.8MediumCNA
Exploited
No known exploitation
Fix
Fixed in 0.29.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 0.29.0.

10Pcve.now Index 10 of 100 · methodology v3 · provisional
  • Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Data gap: No advisory context yet
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity6.8/10CVSS 6.8
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

CVE-2026-91168 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.8 (medium) and affects warpgate; fixed in 0.29.0.

Published
Last modified
Published
Not listed in CISA KEV
10/100 · provisional
Fix
Fixed in 0.29.0
None on Exploit-DB, Metasploit or GitHub

Summary

Warpgate, an open source SSH, HTTPS, and MySQL bastion host for Linux, has a flaw in its Kubernetes request handling that lets an attacker with a low-privilege account reach the cluster over the network after logging in. An attacker who deletes and recreates an account under the same username can reuse a previous account's still-valid authorization to reach Kubernetes targets, potentially reading cluster resources or making unauthorized changes.

Read the original description

Warpgate is an open source SSH, HTTPS, and MySQL bastion host for Linux. From 0.21.0 until 0.29.0, the Kubernetes request correlator in warpgate-protocol-kubernetes/src/correlator.rs keys an authorized AdmittedTarget by username, target_name, and client IP rather than by the immutable user UUID, while KubernetesSessionHandle::close does not evict the entry. If an account is deleted and a different low-privilege account is created with the same username, the replacement account can successfully authenticate as that recreated username and reuse the predecessor's still-live correlation entry when requesting the same target from the same client IP before kubernetes.session_max_age expires. Current-request authentication still occurs, but the reused entry bypasses a fresh target authorization check and can cause Warpgate to proxy requests with Kubernetes target credentials that the replacement account is not authorized to use, exposing cluster resources or permitting unauthorized mutations. This issue is fixed in version 0.29.0.

What to do

  • Upgrade to a fixed version: 0.29.0.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • warp-tech warpgate

    From 0.21.0 · fixed in 0.29.0

Evidence 3

  1. Advisory
  2. Repository
  3. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-91168

Is CVE-2026-91168 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-91168?

warpgate: from 0.21.0 before 0.29.0.Source: cve.now feed data

How do I fix CVE-2026-91168?

Upgrade to a fixed version: 0.29.0.Source: cve.now feed data