Skip to main content
← Vulnerabilities

Warpgate: Kubernetes listener discloses internal error text to an unauthenticated caller

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

3.7LowCNA
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.

21Pcve.now Index 21 of 100 · methodology v3 · provisional
  • Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Data gap: No advisory context yet
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity3.7/10CVSS 3.7
  • No patch0/5No signal

What would change the score

  • Would score about 66 if added to CISA KEV
  • Would score about 61 if CISA's SSVC rates exploitation active
  • Would score about 26 if advisories confirm default setups are exposed

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

Published
Last modified
Published
Not listed in CISA KEV
21/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 protocol listener that causes internal error details to be returned in HTTP 500 responses. An unauthenticated attacker on the network can trigger these failures remotely, without logging in, and receive internal diagnostics such as parser and database error text, though the attempts are not recorded in the gateway log.

Read the original description

Warpgate is an open source SSH, HTTPS, and MySQL bastion host for Linux. Prior to 0.29.0, the Kubernetes protocol listener uses AcceptAnyClientCert in warpgate-protocol-kubernetes/src/server/client_certs.rs to accept certificates at the TLS layer and defer validation to warpgate-protocol-kubernetes/src/server/auth.rs, where authentication and lookup failures are rendered verbatim in an HTTP 500 response body. The Kubernetes application in warpgate-protocol-kubernetes/src/server/mod.rs lacks the outer request-logging wrapper used by the HTTP protocol, and failures in warpgate-protocol-kubernetes/src/server/handlers.rs can short-circuit before its inner log point. An unauthenticated network client can therefore induce failures and receive ASN.1/DER parser diagnostics or sea_orm database errors without the attempt being recorded in the gateway log. The disclosed information is limited to internal diagnostics, and no user-data, integrity, or availability impact is established. 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

    fixed in 0.29.0

Evidence 4

  1. Advisory
  2. Repository
  3. Repository
  4. Repository

Corrections

None so far.

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

FAQ

Questions about CVE-2026-91163

Is CVE-2026-91163 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-91163?

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

How do I fix CVE-2026-91163?

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