CVE-2026-101090

published 27 Sep 2026 · updated 28 Sep 2026

Nezha through 2.2.3 Host Header Injection via OAuth2 redirect_uri

9.8CriticalCVSS 9.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

Nezha 2.2.3 contains a Host header injection regression in the OAuth2 redirect endpoint. When the new optional dashboard_host setting is empty, /api/v1/oauth2/{provider} (cmd/dashboard/controller/oauth2.go) reflects the attacker-supplied HTTP Host header into the redirect_uri sent to the identity provider instead of falling back to the configured install_host. An attacker who induces a victim to begin OAuth2 login via a request that reaches Nezha with a forged Host header can cause an attacker-controlled callback URL to be used as the redirect_uri; if the OAuth2 provider accepts it, the victim's authorization code is delivered to the attacker origin, allowing the attacker to complete the OAuth2 login/binding flow and take over the account. This regresses the fix for GHSA-9rc6-8cjv-rcvx and is configuration-dependent (dashboard_host empty). At the time of the advisory no patched version was available.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
nezhahq>=2.2.3 <=2.2.3

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-101090 severity on Zeptric[![CVE-2026-101090](https://zeptric.io/badge/cve/CVE-2026-101090.svg)](https://zeptric.io/cve/CVE-2026-101090)