Quick answers
- Is CVE-2026-101085 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-101085 being exploited in the wild.
- How severe is CVE-2026-101085?
- Medium severity, with a CVSS score of 6.5, published 27 September 2026.
- Which products and versions are affected?
- Nezha before 2.3.8.
- Is there a fix for CVE-2026-101085?
- A patch was published on 2026-09-27: Version 2.3.8 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-101085 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-101085?
- Check whether you run Nezha at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability stems from insufficient validation in the validateRule() function, which fails to check Rule.Type against a known allowlist and does not properly bound Rule.Duration (a uint64 field). An attacker can craft a rule with invalid type values ("gpu_max", "temperature_max") or an excessively large Duration value that triggers a panic in the unprotected alert evaluator goroutine. Because checkStatus() lacks a recover() block and runs as a bare goroutine outside the request path, the panic is fatal and crashes the entire dashboard process, which also serves the agent gRPC control plane.
Affected products
- Nezha Nezha before 2.3.8
Timeline
- 2026-09-27: disclosed
- 2026-09-27: patched: Version 2.3.8 released