CVE-2026-53519
Received Received - Intake
Path Traversal in Nezha Monitoring Dashboard

Publication date: 2026-06-12

Last updated on: 2026-06-12

Assigner: GitHub, Inc.

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 Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-12
Last Modified
2026-06-12
Generated
2026-06-13
AI Q&A
2026-06-13
EPSS Evaluated
N/A
NVD
CVE-2026-53519
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
nezha_monitoring nezha_monitoring to 2.0.13 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in Nezha Monitoring versions prior to 2.0.13. The dashboard's NoRoute handler uses a flawed method to identify admin-frontend asset requests by checking if the URL starts with '/dashboard' using a simple string prefix check. This allows specially crafted URLs like '/dashboard../data/config.yaml' to bypass intended restrictions. The system then normalizes the path, which results in access to files outside the admin directory. Because there is no authentication required, an attacker can exploit this to read arbitrary files on the server.

Compliance Impact

The vulnerability allows unauthenticated access to sensitive configuration files due to improper path handling in the Nezha Monitoring dashboard. This can lead to unauthorized disclosure of sensitive information.

Such unauthorized data exposure could potentially violate data protection regulations like GDPR or HIPAA, which require strict controls on access to sensitive data and personal information.

However, the provided information does not explicitly state the impact on compliance with these standards.

Detection Guidance

This vulnerability can be detected by checking if the Nezha Monitoring instance is running a version prior to 2.0.13 and if it improperly serves files when accessing URLs starting with /dashboard that include path traversal sequences.

One way to detect exploitation attempts is to send HTTP requests to the Nezha Monitoring dashboard endpoint with crafted URLs that include path traversal patterns such as /dashboard../data/config.yaml and observe if sensitive files are served without authentication.

Example command using curl to test for this vulnerability:

  • curl -i http://<nezha-monitoring-host>/dashboard../data/config.yaml

If the response contains contents of sensitive files like config.yaml without authentication, the system is vulnerable.

Impact Analysis

This vulnerability can lead to unauthorized disclosure of sensitive files on the server. Since no authentication is required to exploit it, an attacker can access configuration files or other sensitive data, potentially exposing secrets, credentials, or other critical information. This can compromise the security and integrity of the monitored systems and the Nezha Monitoring installation.

Mitigation Strategies

The vulnerability has been patched in Nezha Monitoring version 2.0.13. The immediate step to mitigate this vulnerability is to upgrade your Nezha Monitoring installation to version 2.0.13 or later.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-53519. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart