# CVE-2026-53520: Nezha Monitoring: Authenticated users can claim the dashboard Host through NAT and preempt all dashboard routing

> Authenticated users can claim the dashboard host via NAT, preempting routing and gaining unauthorized control over the monitoring interface.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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-x6fg-52vr-hj4w, GO-2026-5824

## What is CVE-2026-53520?

CVE-2026-53520 is a medium-severity missing authorization 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 2.0.14 to before version 2.1.0, authenticated users can claim the dashboard Host through NAT and preempt all dashboard routing. This issue has been patched in version 2.1.0.

Weakness: CWE-284 (Improper Access Control)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/nezhahq/nezha` | Go | All versions | None |
| `github.com/nezhahq/nezha` | Go | From 2.0.14 | 2.1.0 |
| `github.com/nezhahq/nezha` | Go | From 2.0.14 | 2.1.0 |

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

Upgrade github.com/nezhahq/nezha to 2.1.0 or later.

## Is CVE-2026-53520 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53520 is a medium-severity missing authorization 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-53520 exists.

Affected packages and fixed versions:
- github.com/nezhahq/nezha (Go): affected all versions; no fix listed
- github.com/nezhahq/nezha (Go): affected from 2.0.14; fixed in 2.1.0
- github.com/nezhahq/nezha (Go): affected from 2.0.14; fixed in 2.1.0

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-53520/ (Markdown: https://insights.sbomify.com/CVE-2026-53520/index.md)
```

## Sources

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

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