{
  "id": "CVE-2026-101090",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-101090",
  "published_at": "2026-09-27T20:50:00.857Z",
  "title": "Nezha through 2.2.3 Host Header Injection via OAuth2 redirect_uri",
  "vendor": "nezhahq",
  "product": "nezha",
  "cvss": {
    "score": 9.8,
    "source": "cna",
    "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "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.",
  "cwe": "CWE-601",
  "cvss_by_source": {
    "cna": 9.8
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "nezhahq",
        "product": "nezha",
        "ranges": [
          "\u003e= 2.2.3, \u003c= 2.2.3"
        ],
        "fixed_in": null
      }
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://github.com/nezhahq/nezha/security/advisories/GHSA-rf68-8gjr-36q7"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
