Quick answers
- Is CVE-2026-120046 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120046 being exploited in the wild.
- How severe is CVE-2026-120046?
- Medium severity, with a CVSS score of 5.3, published 30 October 2026.
- Which products and versions are affected?
- Nezha 2.0.0 before 2.4.0.
- Is there a fix for CVE-2026-120046?
- Yes: fixed in 2.4.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-120046 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-120046?
- 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.
How to fix
- Fixed in: 2.4.0
Technical details
A NULL pointer dereference vulnerability exists in the ServiceSentinel.loadTodayStats function. An authenticated user can delete their own service via POST /api/v1/batch-delete/service, leaving orphaned service_history rows in the database. When the non-TSDB dashboard restarts and calls loadTodayStats, it dereferences a NULL pointer while processing these orphaned records, causing a crash. This requires prior authentication but no special privileges beyond ability to delete one's own service.
Affected products
- Nezha Nezha 2.0.0 before 2.4.0
Timeline
- 2026-10-30: disclosed