# CVE-2026-63329: Auth bypass in warpgate

> An authenticated attacker can spoof their identity by injecting reserved headers, allowing them to access backend services as another user.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-862h-v6cc-9757

## What is CVE-2026-63329?

CVE-2026-63329 is a medium-severity authentication bypass vulnerability in warp-tech warpgate, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-290 (Authentication Bypass by Spoofing), CWE-116 (Improper Encoding or Escaping of Output)

## Which versions are affected by CVE-2026-63329?


## How do I fix CVE-2026-63329?

No fix has been published for CVE-2026-63329 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-63329 being exploited?

There is no known exploitation of CVE-2026-63329 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63329 and fix it if it is affected.

What it is: CVE-2026-63329 is a medium-severity authentication bypass vulnerability in warp-tech warpgate, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-63329 in the wild and no public exploit code.

Affected product: warp-tech warpgate. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63329/ (Markdown: https://insights.sbomify.com/CVE-2026-63329/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63329
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63329
- OSV: https://osv.dev/vulnerability/CVE-2026-63329

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63329/
Summaries are generated and may contain mistakes; the official description above is the record.