Skip to main content
VulnerabilityPublished

CVE-2026-101086: nezhahq nezha · Improper Privilege Management

Affects nezhahq nezhaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 2.3.5 soon.

Data as of 11 Nov 2026, 23:24 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.3.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

What to do

Upgrade nezha and nezhahq/nezha to 2.3.5.

Affected software

ProductAffectedFixed in
nezhahqnezhaAffected
  • <2.3.5
Fixed in
  • 2.3.5
GitHubnezhahq/nezhapkg:github/nezhahq/nezhaOther threatsAffected
  • <2.3.5
Fixed in
  • 2.3.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Nezha Dashboard version 2.3.5. Users should upgrade to version 2.3.5 or later to remediate this vulnerability. No additional mitigation guidance is provided or required beyond applying the official fix.

Description

Nezha Dashboard versions before 2.3.5 fail to restrict service monitor task types to supported probe types, allowing authenticated users with nezha:service:write scope to submit privileged task types through the service API. Attackers can deliver command execution or Agent configuration tasks to Agents within their authorization scope by exploiting the shared protobuf Task.Type namespace between service monitors and privileged operations.

References

Community reviews

Loading reviews…