CVE-2026-53519: nezhahq nezha · Path Traversal
Affects nezhahq nezhaSource CVE Database V5
Not known to be exploited · public detection template (Nuclei) · CVSS 9.1 Critical : upgrade to 2.0.13 as a priority.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 1.9% chance of exploitation in 30 days – higher than 79% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.0.13
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Jun 2026
Detectable: evidence found.
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade nezha and nezhahq/nezha to 2.0.13.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nezhahqnezha | Affected
| Fixed in
|
GitHubnezhahq/nezhapkg:github/nezhahq/nezhaOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in Nezha Monitoring version 2.0.13. Users should upgrade to version 2.0.13 or later to remediate this issue. No other mitigation is indicated or required.
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.