CVE-2026-101090
criticalNezha 2.2.3 contains a Host header injection regression in the OAuth2 redirect endpoint.
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Affected products
Not reported by the source (unknown — not "none").
Weakness classification (CWE)
Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.
Mitigation & advisories
No vendor advisory or patch reference tagged by NVD. Check the references below.
References
- https://github.com/nezhahq/nezha/security/advisories/GHSA-rf68-8gjr-36q7 disclosure@vulncheck.com
- https://www.vulncheck.com/advisories/nezha-through-2.2.3-host-header-injection-via-oauth2-... disclosure@vulncheck.com
- https://github.com/nezhahq/nezha/security/advisories/GHSA-rf68-8gjr-36q7 134c704f-9b21-4f2e-91b3-4a467353bcc0
