Is CVE-2026-53519 exploited in the wild?

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

How severe is CVE-2026-53519?

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

Which products and versions are affected?

github.com/nezhahq/nezha (Go) < 2.0.13, SEMVER:introduced=0, SEMVER:introduced=0,fixed=2.0.13; NezhaHQ Nezha Monitoring < 2.0.13.

Is there a fix for CVE-2026-53519?

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

How is CVE-2026-53519 attacked?

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

Am I affected by CVE-2026-53519?

Check whether you run github.com/nezhahq/nezha (Go) or NezhaHQ Nezha Monitoring 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-53519: Nezha Monitoring path traversal in dashboard NoRoute handler

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

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

Q: How is CVE-2026-53519 attacked?

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

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

Check whether you run github.com/nezhahq/nezha (Go) or NezhaHQ Nezha Monitoring 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-53519 · Severity: critical · CVSS 9.1 · Published 2026-06-12

Nezha Monitoring is a dashboard used for server and service monitoring. A security flaw allows unauthenticated attackers to access sensitive configuration files and the system database by sending a specially crafted web request. This can lead to the theft of secret keys and administrative credentials, allowing an attacker to take full control of the monitoring dashboard and its managed data.

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

Quick answers

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

Technical details

A path traversal vulnerability exists in the 'fallbackToFrontend' handler of Nezha Monitoring due to improper URL prefix validation. The application uses 'strings.HasPrefix' to check for '/dashboard' without ensuring a proper path segment match, allowing requests like '/dashboard../' to bypass standard Go 'http.ServeFile' security guards. When processed, 'path.Join' normalizes the traversal, allowing an unauthenticated attacker to read files outside the intended directory. This primitive can be used to exfiltrate 'data/config.yaml' (containing the HS256 'jwt_secret_key') and 'data/sqlite.db', enabling the attacker to forge administrative JWTs and achieve full system compromise. The issue is fixed in version 2.0.13.

Affected products

nezhahq Nezha Monitoring < 2.0.13

Identifiers

CVE-2026-53519
GHSA-5c25-7vpj-9mqh
GO-2026-5828

Timeline

2026-05-31: disclosed
2026-06-26: advisory: Updated advisory published

References

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