Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 2.9amended

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

CVE-2026-101090GHSA-rf68-8gjr-36q7

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/nezhahq/nezha

    Affected
    >= 2.2.3, <= 2.2.3
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
2.9 · CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:P · score source
EPSS
  • CVE-2026-101090: 0.44% estimated exploitation activity in the next 30 days; percentile 38.60 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Nezha v2.2.3 regresses the GHSA-9rc6-8cjv-rcvx host header injection fix for deployments where the new dashboardhost setting is empty. In that configuration, /api/v1/oauth2/{provider} again reflects the request Host header into the OAuth2 redirecturi sent to the identity provider, even if installhost is configured. Impact An attacker who can get a victim to start OAuth2 login through a request that reaches Nezha with a forged Host header can make Nezha send an attacker-controlled callback URL as the OAuth2 redirecturi. If the configured OAuth2 provider accepts that redirect URI, the victim's authorization code is sent to the attacker origin. The attacker can then complete the OAuth2 binding or login flow described in GHSA-9rc6. This is configuration-dependent, but it affects a realistic upgrade/default state because dashboardhost is a new optional field. The original v2.2.0 fix fell back to installhost; current v2.2.3 only falls back when dashboardhost is non-empty.…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-rf68-8gjr-36q7

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6486

  4. Revision 1 · created ·

    Published from osv record GHSA-rf68-8gjr-36q7

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-101090

Advisory: Nezha: OAuth2 redirect_uri Host header injection regression when dashboard_host is empty
IDs: CVE-2026-101090, GHSA-rf68-8gjr-36q7
Record: https://patchnext.com/advisories/cve-2026-101090 (revision 4, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/nezhahq/nezha: affected >= 2.2.3, <= 2.2.3

## Suggested inspection (read-only)
- Go github.com/nezhahq/nezha: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/nezhahq/nezha.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-rf68-8gjr-36q7 (OSV record GHSA-rf68-8gjr-36q7 lists affected ranges: Go github.com/nezhahq/nezha >=2.2.3 <=2.2.3)
- Verified: https://osv.dev/vulnerability/GO-2026-6486 (OSV record GO-2026-6486 lists affected ranges: Go github.com/nezhahq/nezha >=0)
- Verified: https://github.com/advisories/GHSA-rf68-8gjr-36q7 (GitHub-reviewed advisory GHSA-rf68-8gjr-36q7 lists affected ranges: Go github.com/nezhahq/nezha >=2.2.3 <=2.2.3)

Commands are suggestions: review each one before running it.

Loading voting…