Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-101090Published 2026-09-27

CVE-2026-101090 — nezhahq nezha

critical

As of 2026-09-28, CVE-2026-101090 is a CRITICAL-severity vulnerability in nezhahq nezha, CVSS v3.1 9.8. No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-101090 as of 2026-09-28; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
9.8/10Critical
EPSS
—No EPSS score yet
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
4.9/10Threadlinqs triage score
Published
Updated 2026-09-28
CVSS v3.1 9.8 (CRITICAL) · CVSS v4.0 9.3 · Priority 4.9/10 · Published 2026-09-27

Last updated:

What is CVE-2026-101090?

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.

The record classifies CVE-2026-101090 under weakness class CWE-601. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 8 days ago.

Severity and exploitation probability

CVSS v3.1 base score
9.8 — CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS v4.0 base score
9.3
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
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
4.9/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-09-27, last modified 2026-09-28

Is CVE-2026-101090 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

Affected products and versions

  • nezhahq: nezha

How to fix CVE-2026-101090

No vendor patch reference has been recorded for CVE-2026-101090 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-101090

No threat campaign in the Threadlinqs corpus currently references CVE-2026-101090, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org. Last verified by Threadlinqs on .

Vendor advisory and patch

Third-party advisory