CVE-2026-53519: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in nezhahq nezha
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.
AI Analysis
Technical Summary
CVE-2026-53519 is a path traversal vulnerability (CWE-22) in Nezha Monitoring before version 2.0.13. The dashboard's NoRoute handler uses strings.HasPrefix to identify admin-frontend asset requests starting with /dashboard, but this check does not enforce path-segment boundaries. An attacker can supply a URL such as /dashboard../data/config.yaml, which after trimming the prefix and joining paths, resolves to a file outside the admin-dist directory. The server then serves this file without authentication, exposing potentially sensitive data. The vulnerability is patched in version 2.0.13.
Potential Impact
An unauthenticated attacker can exploit this vulnerability to read arbitrary files on the server hosting Nezha Monitoring by crafting specially formed URLs. This can lead to disclosure of sensitive configuration or data files, impacting confidentiality. There is no indication of impact on integrity or availability.
Mitigation Recommendations
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.
CVE-2026-53519: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in nezhahq nezha
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.
CVSS v3.1
Score 9.1critical
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-53519 is a path traversal vulnerability (CWE-22) in Nezha Monitoring before version 2.0.13. The dashboard's NoRoute handler uses strings.HasPrefix to identify admin-frontend asset requests starting with /dashboard, but this check does not enforce path-segment boundaries. An attacker can supply a URL such as /dashboard../data/config.yaml, which after trimming the prefix and joining paths, resolves to a file outside the admin-dist directory. The server then serves this file without authentication, exposing potentially sensitive data. The vulnerability is patched in version 2.0.13.
Potential Impact
An unauthenticated attacker can exploit this vulnerability to read arbitrary files on the server hosting Nezha Monitoring by crafting specially formed URLs. This can lead to disclosure of sensitive configuration or data files, impacting confidentiality. There is no indication of impact on integrity or availability.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-09T17:30:33.456Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a2c7c90e617e2d834c6c7bb
Added to database: 06/12/2026, 21:39:28 UTC
Last enriched: 06/19/2026, 22:19:42 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 361
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.