CVE-2026-53519

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.9%, top 23% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 9.1Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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
9.1
EG Score
9.1(medium)
EG Risk
72(Track)
EG Risk 72/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
77%
KEV
Not listed

Published

June 12, 2026

Last Modified

June 15, 2026

Advisory Details (1)

Auto-updated Aug 1, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Pre-auth path traversal via /dashboard.. prefix confusion leaks jwt_secret_key · Advisory · nezhahq/nezha · GitHub

https://github.com/nezhahq/nezha/security/advisories/GHSA-5c25-7vpj-9mqh

Vendor Advisories for CVE-2026-53519(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/nezhahq/nezha—2.0.13—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 53× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 117 total refreshes for this CVE.

  1. 2026-08-23 09:57 UTCEG score recompute
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-21 01:11 UTCEG score recompute
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-20 08:45 UTCEG score recompute
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 13:34 UTCEG score recompute
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-16 17:08 UTCEG score recompute
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 03:59 UTCEG score recompute
  14. 2026-08-16 02:14 UTCEPSS rescore
  15. 2026-08-15 04:51 UTCEG score recompute
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-13 22:11 UTCEG score recompute
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-12 15:56 UTCEG score recompute
  20. 2026-08-12 13:51 UTCEPSS rescore
  21. 2026-08-11 17:58 UTCEG score recompute
  22. 2026-08-11 00:06 UTCEG score recompute
  23. 2026-08-11 00:00 UTCEPSS rescore
  24. 2026-08-09 15:54 UTCEG score recompute
  25. 2026-08-09 13:46 UTCEPSS rescore
Show 75 more
  1. 2026-08-08 17:58 UTCEG score recompute
  2. 2026-08-08 16:37 UTCEPSS rescore
  3. 2026-08-07 20:05 UTCEG score recompute
  4. 2026-08-06 17:48 UTCEG score recompute
  5. 2026-08-06 13:47 UTCEPSS rescore
  6. 2026-08-05 19:54 UTCEG score recompute
  7. 2026-08-05 19:17 UTCEPSS rescore
  8. 2026-08-04 15:45 UTCEG score recompute
  9. 2026-08-04 15:10 UTCEPSS rescore
  10. 2026-08-04 10:39 UTCEPSS rescore
  11. 2026-08-03 14:46 UTCEG score recompute
  12. 2026-08-03 10:36 UTCEPSS rescore
  13. 2026-08-02 02:44 UTCEG score recompute
  14. 2026-08-02 02:27 UTCEPSS rescore
  15. 2026-08-01 09:11 UTCEG score recompute
  16. 2026-08-01 04:16 UTCEPSS rescore
  17. 2026-07-31 00:09 UTCEG score recompute
  18. 2026-07-30 16:28 UTCEPSS rescore
  19. 2026-07-30 10:28 UTCEG score recompute
  20. 2026-07-30 06:05 UTCEG score recompute
  21. 2026-07-30 01:30 UTCEPSS rescore
  22. 2026-07-29 04:14 UTCEG score recompute
  23. 2026-07-28 15:37 UTCEPSS rescore
  24. 2026-07-27 18:20 UTCEG score recompute
  25. 2026-07-26 20:28 UTCEG score recompute
  26. 2026-07-26 14:54 UTCEPSS rescore
  27. 2026-07-25 14:18 UTCEPSS rescore
  28. 2026-07-24 14:18 UTCEPSS rescore
  29. 2026-07-23 14:18 UTCEPSS rescore
  30. 2026-07-23 03:19 UTCEG score recompute
  31. 2026-07-22 14:08 UTCEPSS rescore
  32. 2026-07-21 15:25 UTCEPSS rescore
  33. 2026-07-20 17:08 UTCEPSS rescore
  34. 2026-07-19 14:31 UTCEPSS rescore
  35. 2026-07-19 14:31 UTCEPSS rescore
  36. 2026-07-19 02:29 UTCEPSS rescore
  37. 2026-07-18 10:04 UTCEPSS rescore
  38. 2026-07-16 17:03 UTCEPSS rescore
  39. 2026-07-15 16:57 UTCEPSS rescore
  40. 2026-07-15 16:57 UTCEPSS rescore
  41. 2026-07-15 02:00 UTCEPSS rescore
  42. 2026-07-15 02:00 UTCEPSS rescore
  43. 2026-07-13 22:31 UTCEPSS rescore
  44. 2026-07-13 06:13 UTCEPSS rescore
  45. 2026-07-13 06:13 UTCEPSS rescore
  46. 2026-07-12 05:46 UTCEPSS rescore
  47. 2026-07-11 08:27 UTCEPSS rescore
  48. 2026-07-11 08:27 UTCEPSS rescore
  49. 2026-07-09 19:10 UTCEPSS rescore
  50. 2026-07-09 19:10 UTCEPSS rescore
  51. 2026-07-08 15:16 UTCEPSS rescore
  52. 2026-07-08 15:16 UTCEPSS rescore
  53. 2026-07-07 13:46 UTCEPSS rescore
  54. 2026-07-07 13:46 UTCEPSS rescore
  55. 2026-07-06 16:27 UTCEPSS rescore
  56. 2026-07-06 16:27 UTCEPSS rescore
  57. 2026-07-06 02:23 UTCEPSS rescore
  58. 2026-07-06 02:23 UTCEPSS rescore
  59. 2026-07-05 02:31 UTCEPSS rescore
  60. 2026-07-05 02:30 UTCEPSS rescore
  61. 2026-07-04 06:31 UTCEPSS rescore
  62. 2026-07-04 06:31 UTCEPSS rescore
  63. 2026-07-01 15:07 UTCEPSS rescore
  64. 2026-06-30 23:22 UTCEPSS rescore
  65. 2026-06-29 14:06 UTCEPSS rescore
  66. 2026-06-29 14:06 UTCEPSS rescore
  67. 2026-06-28 14:07 UTCEPSS rescore
  68. 2026-06-28 04:56 UTCEPSS rescore
  69. 2026-06-28 04:56 UTCEPSS rescore
  70. 2026-06-27 03:08 UTCEPSS rescore
  71. 2026-06-25 13:49 UTCEPSS rescore
  72. 2026-06-24 14:05 UTCEPSS rescore
  73. 2026-06-23 21:33 UTCEPSS rescore
  74. 2026-06-23 21:33 UTCEPSS rescore
  75. 2026-06-22 14:25 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCtar-xz/CVE-2026-53519-PoC
    First seen Jun 15, 2026

    PoC exploit for CVE-2026-53519.

    Open source ↗
  • Nucleihttp/cves/2026/CVE-2026-53519.yaml
    First seen Jan 1, 2026

    Nezha Dashboard < 2.0.13 - Path Traversal

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53519?
CVE-2026-53519 is a critical vulnerability published on June 12, 2026. 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,…
When was CVE-2026-53519 disclosed?
CVE-2026-53519 was first published in the National Vulnerability Database on June 12, 2026, with the most recent update on June 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53519 actively exploited?
CVE-2026-53519 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 22.5% of all scored CVEs.
What is the CVSS score of CVE-2026-53519?
CVE-2026-53519 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-53519?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53519, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53519

Explore →

Is Your Infrastructure Affected by CVE-2026-53519?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs