# CVE-2026-53519: Nezha Monitoring: Pre-auth path traversal via /dashboard.. prefix confusion leaks jwt_secret_key

> Unauthenticated attackers can read sensitive configuration files, including JWT secrets, via path traversal in the dashboard handler.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-5c25-7vpj-9mqh, GO-2026-5828

## What is CVE-2026-53519?

CVE-2026-53519 is a critical path traversal vulnerability in nezhahq nezha, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool. Prior to version 2.0.13, fallbackToFrontend in the dashboard's NoRoute handler treats any URL whose raw string starts with /dashboard as an admin-frontend asset request. The check uses strings.HasPrefix, not a path-segment match, so the input /dashboard../data/config.yaml is accepted; strings.TrimPrefix leaves ../data/config.yaml; and path.Join("admin-dist", "../data/config.yaml") normalizes to data/config.yaml — which os.Stat finds and http.ServeFile returns. No authentication required. This issue has been patched in version 2.0.13.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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 | All versions | 2.0.13 |
| `github.com/nezhahq/nezha` | Go | All versions | 2.0.13 |

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

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

## Is CVE-2026-53519 being exploited?

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

Public exploit code:

- PoC exploit for CVE-2026-53519. (github_poc): https://github.com/tar-xz/CVE-2026-53519-PoC
- https://github.com/ivanesk315/CVE-2026-53519 (github_poc): https://github.com/ivanesk315/CVE-2026-53519
- Nezha Dashboard < 2.0.13 - Path Traversal (nuclei): http/cves/2026/CVE-2026-53519.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53519 is a critical path traversal vulnerability in nezhahq nezha, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53519 exists.

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

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

## Sources

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

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