CVE-2026-63329

Warpgate: x-warpgate-username Header Not Stripped from Client Requests Enables Identity Spoofing to WebSocket Backend Targets

Published Sep 21, 2026 CVSS 3.1 · 4.9 Medium EPSS < 1% KEV · Not listed
Description
Warpgate is an open source SSH, HTTPS and MySQL bastion host for Linux. Prior to 0.25.6, copy_server_request in warpgate-protocol-http/src/proxy.rs forwards a client-supplied x-warpgate-username header before inject_own_headers appends the authenticated username. Because the request builder preserves repeated values, a proxied backend that trusts the first x-warpgate-username value can authorize an authenticated attacker as another user. The same forwarding policy also accepts the reserved x-warpgate-authentication-type header, and warpgate-common/src/http_headers.rs does not exclude either reserved identity header. This issue is fixed in version 0.25.6.

Analysis

AI-generated

Technical impact

A client can supply a forged x-warpgate-username or x-warpgate-authentication-type header that the proxy forwards to the backend before its own authenticated user header is added. Because the request builder preserves repeated header values, a backend that trusts the first value can authenticate the attacker as any user. This flaw allows an attacker who can send a request through Warpgate to impersonate other users on the target backend service, undermining confidentiality of user data and potentially enabling further compromise.

Affected Systems

Warp‑Tech Warpgate software versions earlier than 0.25.6 are affected. The vulnerability exists in the copy_server_request handler in warpgate-protocol-http and is fixed in release 0.25.6 and later.

Risk and Exploitability

The CVSS score is 4.9, indicating a moderate severity. No EPSS data is available and the vulnerability has not been listed in CISA’s KEV catalog. The likely attack vector is an authenticated user who can inject the spoofed headers into a forwarded request; no additional preconditions beyond a valid session to Warpgate are required. Attackers can then exploit backend trust of those headers to acquire unauthorized access.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Warpgate to version 0.25.6 or later where the header forwarding issue is fixed
  • If an upgrade is not immediately possible, reconfigure Warpgate to omit the x-warpgate-username and x-warpgate-authentication-type headers from forwarded requests
  • Ensure that backend services do not rely on these headers for user authentication; implement explicit user validation based on the authenticated session rather than forwarded header values

Generated by OpenCVE AI on September 21, 2026 at 20:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Warp-tech
Warp-tech warpgate
Vendors & Products Warp-tech
Warp-tech warpgate
Type Values Removed Values Added
Description Warpgate is an open source SSH, HTTPS and MySQL bastion host for Linux. Prior to 0.25.6, copy_server_request in warpgate-protocol-http/src/proxy.rs forwards a client-supplied x-warpgate-username header before inject_own_headers appends the authenticated username. Because the request builder preserves repeated values, a proxied backend that trusts the first x-warpgate-username value can authorize an authenticated attacker as another user. The same forwarding policy also accepts the reserved x-warpgate-authentication-type header, and warpgate-common/src/http_headers.rs does not exclude either reserved identity header. This issue is fixed in version 0.25.6.
Title Warpgate: x-warpgate-username Header Not Stripped from Client Requests Enables Identity Spoofing to WebSocket Backend Targets
Weaknesses CWE-116
CWE-290
References
Metrics cvssV3_1

{'score': 4.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N'}

Weaknesses
  • CWE-116

    Improper Encoding or Escaping of Output

  • CWE-290

    Authentication Bypass by Spoofing

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Sep 22, 2026, 3:40 PM
Reserved
Jul 16, 2026, 2:14 PM
Status
Deferred
Published
Sep 21, 2026, 7:17 PM
Modified
Sep 24, 2026, 9:25 PM