dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-53519

CRITICAL · 9.1 CVSS v3.1 Published 2026-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Nezha Monitoring versions before 2.0.13 contain a path traversal vulnerability in the dashboard's NoRoute handler. The handler incorrectly uses strings.HasPrefix to check if URLs start with /dashboard, allowing attackers to bypass this check with /dashboard../data/config.yaml. This string manipulation results in path.Join normalizing to data/config.yaml, enabling unauthenticated arbitrary file read including sensitive configuration files.

MitigationUpgrade Nezha Monitoring to version 2.0.13 or later to patch the path traversal vulnerability. If immediate upgrade is not possible, consider restricting access to the dashboard endpoint via network-level controls or a WAF.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Nezha Monitoring is installed
    Check for running Nezha processes using 'ps aux | grep nezha' or check for the service via 'systemctl list-units | grep nezha' or 'docker ps | grep nezha'
    Affected if Nezha Monitoring process or service is found running on the system
  2. Identify installed Nezha version
    Run 'nezha-agent --version' or 'nezha-server --version' depending on component, or check the Docker image tag if running containers, or inspect the binary file metadata
    Affected if Version returned is below 2.0.13 (e.g., 2.0.12, 2.0.10, etc.)
  3. Verify dashboard endpoint is network-accessible
    Attempt to access http://[your-server]/dashboard or https://[your-server]/dashboard from an external host, or check firewall rules and reverse proxy configuration for dashboard route exposure
    Affected if Dashboard endpoint responds to HTTP requests from untrusted networks
  4. Check for sensitive configuration files
    Verify that data/config.yaml or other sensitive configuration files exist in the Nezha data directory accessible to the application
    Affected if Sensitive configuration files exist and are readable by the Nezha process user

You are affected if Nezha Monitoring version is below 2.0.13 AND the dashboard endpoint is network-accessible, allowing an attacker to exploit the path traversal to read sensitive files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Nezha Monitoring to version 2.0.13 or later to patch the path traversal vulnerability. If immediate upgrade is not possible, consider restricting access to the dashboard endpoint via network-level controls or a WAF.

Recommended fix High confidence

2.0.13

  1. 1. Back up your current Nezha Monitoring installation and configuration data.
  2. 2. Stop the Nezha Monitoring service.
  3. 3. Download version 2.0.13 or later from the official Nezha Monitoring GitHub repository.
  4. 4. Replace the existing installation files with the new version.
  5. 5. Review release notes for any required configuration changes.
  6. 6. Start the Nezha Monitoring service.
  7. 7. Verify the installation by accessing the dashboard and confirming normal operation.
Caveat Review the 2.0.13 release notes for any configuration or feature changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53519 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53519 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data