Skip to main content
VulnerabilityPublished

CVE-2026-91168: warp-tech warpgate · Insecure Direct Object Reference

Affects warp-tech warpgateSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.8 Medium : upgrade to 0.29.0 when convenient.

Data as of 4 Nov 2026, 15:43 UTC

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.16.8
Patch
Available – fixed in 0.29.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

What to do

Upgrade warp-tech warpgate to 0.29.0.

Affected software

ProductAffectedFixed in
warp-techwarpgateAffected
  • >=0.21.0 <0.29.0
Fixed in
  • 0.29.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Warpgate to version 0.29.0 or later, where this authorization bypass vulnerability is fixed. No other mitigations are indicated by the vendor advisory. Applying the official fix fully addresses the issue.

Description

Warpgate versions from 0.21.0 up to but not including 0.29.0 contain an authorization bypass vulnerability in the Kubernetes request correlator. The flaw arises because authorization keys are based on mutable user identifiers (username, target_name, client IP) instead of immutable user UUIDs, and session entries are not properly evicted when accounts are deleted. This allows a low-privilege replacement account with the same username to reuse a predecessor's session entry and bypass fresh authorization checks, potentially accessing or modifying Kubernetes cluster resources without proper permission. The issue is fixed in version 0.29.0.

References

Community reviews

Loading reviews…