Is CVE-2026-46716 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-46716 being exploited in the wild.

How severe is CVE-2026-46716?

Critical severity, with a CVSS score of 9.9, published 12 June 2026.

Which products and versions are affected?

github.com/nezhahq/nezha (Go) >= 1.4.0, = 1.4.0, < 2.0.8.

Is there a fix for CVE-2026-46716?

Yes. github.com/nezhahq/nezha (Go): upgrade to 1.14.15-0.20260517022419-d7526351cf97 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-46716 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-46716?

Check whether you run github.com/nezhahq/nezha (Go), NezhaHQ Nezha Monitoring or NezhaHQ Nezha Monitoring Dashboard 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.

CVE-2026-46716: Nezha Monitoring Cross-Tenant RCE via Cron Task API

Q: Is there a fix for CVE-2026-46716?

Yes. github.com/nezhahq/nezha (Go): upgrade to 1.14.15-0.20260517022419-d7526351cf97 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-46716 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-46716?

Check whether you run github.com/nezhahq/nezha (Go), NezhaHQ Nezha Monitoring or NezhaHQ Nezha Monitoring Dashboard 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.

CVE-2026-46716 · Severity: critical · CVSS 9.9 · Published 2026-06-12

Nezha Monitoring is a tool used to manage and monitor servers and websites. A security flaw allows any registered user to execute arbitrary commands on every server managed by the system, including those belonging to other users or administrators. This could lead to a total compromise of all monitored infrastructure and the theft of sensitive data from those servers.

Technologies: github.com/nezhahq/nezha (Go), NezhaHQ Nezha Monitoring. Vendors: Go, NezhaHQ.

Quick answers

Is CVE-2026-46716 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-46716 being exploited in the wild.
How severe is CVE-2026-46716?: Critical severity, with a CVSS score of 9.9, published 12 June 2026.
Which products and versions are affected?: github.com/nezhahq/nezha (Go) >= 1.4.0, < 1.14.15-0.20260517022419-d7526351cf97, SEMVER:introduced=1.4.0,fixed=1.14.15-0.20260517022419-d7526351cf97; NezhaHQ Nezha Monitoring 1.4.0 to 2.0.7; NezhaHQ Nezha Monitoring Dashboard >= 1.4.0, < 2.0.8.
Is there a fix for CVE-2026-46716?: Yes. github.com/nezhahq/nezha (Go): upgrade to 1.14.15-0.20260517022419-d7526351cf97 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-46716 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-46716?: Check whether you run github.com/nezhahq/nezha (Go), NezhaHQ Nezha Monitoring or NezhaHQ Nezha Monitoring Dashboard 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

github.com/nezhahq/nezha (Go): upgrade to 1.14.15-0.20260517022419-d7526351cf97 or later
```
go get github.com/nezhahq/nezha@v1.14.15-0.20260517022419-d7526351cf97
```

Technical details

A cross-tenant Remote Code Execution (RCE) vulnerability exists in Nezha Monitoring versions 1.4.0 through 2.0.7. The issue stems from the '/api/v1/cron' endpoints being accessible via 'commonHandler' (any authenticated user) rather than 'adminHandler'. Additionally, a logic flaw in 'ServerShared.CheckPermission' allows users to bypass server ownership checks by submitting an empty server list. When 'Cover' is set to 'CronCoverAll', the scheduler iterates through the global 'ServerShared' map and pushes the command to every agent in the deployment, regardless of ownership. Attackers can exfiltrate command output by configuring a 'NotificationGroup' with a webhook they control. This has been patched in version 2.0.8.

Affected products

nezhahq Nezha Monitoring 1.4.0 to 2.0.7

Identifiers

CVE-2026-46716
GHSA-99gv-2m7h-3hh9
GO-2026-5282

Timeline

2026-05-17: advisory: GitHub Security Advisory published
2026-06-12: disclosed: NVD publication date
2026-05-17: patched: Fix released in version 2.0.8

References

https://github.com/nezhahq/nezha/security/advisories/GHSA-99gv-2m7h-3hh9

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.