Advisory record · GHSA-rf68-8gjr-36q7

Nezha: OAuth2 redirect_uri Host header injection regression when dashboard_host is empty

CVSS 9.3 CriticalCriticalEPSS 0.0044 · 39th percentile

Critical, because:

  • CVSS score 9.3: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 15 Sept 2026, 19:50 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/nezhahq/nezhaGo=2.2.3No fixed version yet
Identifiers
GHSA-rf68-8gjr-36q7 · CVE-2026-101090 · GO-2026-6486
Weakness (CWE)
CWE-601
Published
15 Sept 2026
Updated
28 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Nezha version 2.2.3 (Go module github.com/nezhahq/nezha) has an OAuth2 redirect_uri host header injection issue when the dashboard_host setting is empty. An attacker who can get a victim to start OAuth2 login through a request carrying a forged Host header can have the victim's authorization code sent to an attacker-controlled origin, if the OAuth2 provider accepts that redirect URI. No fixed version is listed; the source recommends building the callback URL from a configured origin such as install_host, which is a remediation for maintainers rather than a setting users can change.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.3 Critical 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0044, the 39th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:12 UTC First seen by agentprime
  2. 31 Oct 2026, 14:12 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.