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

Published Sep 21, 2026
·
Updated

Warpgate is an open source SSH, HTTPS and MySQL bastion host for Linux. Prior to 0.25.6, copyserverrequest in warpgate-protocol-http/src/proxy.rs forwards a client-supplied x-warpgate-username header before injectownheaders 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/httpheaders.rs does not exclude either reserved identity header. This issue is fixed in version 0.25.6.

Affected Software

1 affected component
warpgate<0.25.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade warpgate-protocol-http/src/proxy.rs / warpgate-protocol-http to a version that resolves this vulnerability.

    Fixed in 0.25.6

Event History

Sep 21, 2026
CVE Published
via MITRE·06:49 PM
Data Sourced
via MITRE·06:49 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to identity spoofing?

Warpgate deployments prior to 0.25.6 are exposed when they proxy requests to a backend that uses the x-warpgate-username header and trusts the first value when repeated header values are present.

2

What does an attacker need to exploit this issue?

The attacker must be authenticated to Warpgate and able to send a client request containing x-warpgate-username. Exploitation also depends on the proxied backend accepting the first repeated header value for authorization.

3

How can I tell whether a backend may be affected?

Review backend handling of x-warpgate-username, particularly whether it uses that header for authorization and selects the first value when multiple instances are received. Requests through affected Warpgate versions can contain both an attacker-supplied value and the authenticated username.

4

What is the remediation?

Upgrade Warpgate to version 0.25.6, which fixes the handling of these reserved identity headers.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203