CVE-2026-25651 client-certificate-auth has an Open Redirect via Host Header Injection in HTTP-to-HTTPS redirect
An attacker can redirect users to arbitrary domains via Host Header Injection in the HTTP-to-HTTPS redirect logic of this Node.js middleware.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-25651?
CVE-2026-25651 is a medium-severity vulnerability in tgies client-certificate-auth, published on 6 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
client-certificate-auth is middleware for Node.js implementing client SSL certificate authentication/authorization. Versions 0.2.1 and 0.3.0 of client-certificate-auth contain an open redirect vulnerability. The middleware unconditionally redirects HTTP requests to HTTPS using the unvalidated Host header, allowing an attacker to redirect users to arbitrary domains. This vulnerability is fixed in 1.0.0.
Weakness: CWE-601
Which versions are affected by CVE-2026-25651?
2 open source packages ship an affected version, including client-certificate-auth. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
client-certificate-auth npm | From 0.2.1 | 1.0.0 |
client-certificate-auth npm | From 0.2.1 | 1.0.0 |
Products include Tgies Client-Certificate-Auth.
How do I fix CVE-2026-25651?
Upgrade client-certificate-auth to 1.0.0 or later.
Is CVE-2026-25651 being exploited?
There is no known exploitation of CVE-2026-25651 in the wild and no public exploit code.
Sources
Also known as GHSA-m4w9-gch5-c2g4.