# CVE-2026-46716: Nezha Monitoring: RoleMember can run shell on every server (cross-tenant RCE) via POST /api/v1/cron

> A low-privileged user can execute arbitrary shell commands on all monitored servers, including those of other tenants, via a crafted cron task.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-99gv-2m7h-3hh9, GO-2026-5282

## What is CVE-2026-46716?

CVE-2026-46716 is a critical command injection vulnerability in nezhahq nezha, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool. From version 1.4.0 to before version 2.0.8, a RoleMember user can create a scheduled cron task with Cover=CronCoverAll, Servers=[] and an arbitrary Command. At every tick of the scheduler, the dashboard pushes that command to every server in the global ServerShared map — including servers that belong to other tenants (admin's servers, other members' servers). Each agent runs the command and returns the output, which is then sent to the attacker's own NotificationGroup → attacker-controlled webhook. This issue has been patched in version 2.0.8.

Weakness: CWE-862 (Missing Authorization), CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-46716?

3 open source packages ship an affected version, including github.com/nezhahq/nezha.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/nezhahq/nezha` | Go | From 1.4.0 | 1.14.15-0.20260517022419-d7526351cf97 |
| `github.com/nezhahq/nezha` | Go | From 1.4.0 | 1.14.15-0.20260517022419-d7526351cf97 |
| `github.com/nezhahq/nezha` | Go | From 1.4.0 | 1.14.15-0.20260517022419-d7526351cf97 |

## How do I fix CVE-2026-46716?

Upgrade github.com/nezhahq/nezha to 1.14.15-0.20260517022419-d7526351cf97 or later.

## Is CVE-2026-46716 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46716 exists.

Public exploit code:

- https://github.com/HAERIN-L/POC_CVE-2026-46716 (github_poc): https://github.com/HAERIN-L/POC_CVE-2026-46716

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46716 and fix it if it is affected.

What it is: CVE-2026-46716 is a critical command injection vulnerability in nezhahq nezha, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46716 exists.

Affected packages and fixed versions:
- github.com/nezhahq/nezha (Go): affected from 1.4.0; fixed in 1.14.15-0.20260517022419-d7526351cf97
- github.com/nezhahq/nezha (Go): affected from 1.4.0; fixed in 1.14.15-0.20260517022419-d7526351cf97
- github.com/nezhahq/nezha (Go): affected from 1.4.0; fixed in 1.14.15-0.20260517022419-d7526351cf97

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46716/ (Markdown: https://insights.sbomify.com/CVE-2026-46716/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46716
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46716
- OSV: https://osv.dev/vulnerability/CVE-2026-46716

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46716/
Summaries are generated and may contain mistakes; the official description above is the record.