Which products and versions are affected by CVE-2026-53519?

Affected: github.com/nezhahq/nezha (go); nezha. The full list is in the CVE brief.

Is CVE-2026-53519 being exploited in the wild?

It is not listed in any known-exploited vulnerabilities catalog.

Is CVE-2026-53519 in the CISA KEV catalog?

No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

Is there a public exploit for CVE-2026-53519?

No public exploit code is known.

Is there a fix for CVE-2026-53519?

Fixed versions are available, including github.com/nezhahq/nezha 2.0.13, nezha 2.0.13.

How urgently should CVE-2026-53519 be patched?

Brandefense priority: patch in the next maintenance window, because of its high severity, although no exploitation is known.

Request A Demo

Vulnerability Intelligence

CVE-2026-53519

Critical

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.

Published Jun 12, 2026 · Updated Aug 12, 2026 · Also known as EUVD-2026-36598, GHSA-5c25-7vpj-9mqh, GO-2026-5828

Key Facts

Patch in the next maintenance window

CVE-2026-53519 is a critical-severity vulnerability (CVSS 9.1 v3.1) affecting github.com/nezhahq/nezha (go), nezha.
It is not listed in any known-exploited vulnerabilities catalog. No public exploit code is known.
EPSS estimates a 2.3% probability of exploitation in the next 30 days.
Fixed versions are available, including github.com/nezhahq/nezha 2.0.13, nezha 2.0.13.
Brandefense priority: patch in the next maintenance window, because of its high severity, although no exploitation is known.

CVSS v3.1

9.1

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

EPSS (30-day exploit likelihood)

2.3%

Exploited in the wild

No known

Not in a known-exploited catalog

Public exploit code

None known

Get the full CVE-2026-53519 brief as a PDF

Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.

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.

Affected Products

2 affected entries in total

Product	Affected versions	Fixed in
github.com/nezhahq/nezhago	See advisory	2.0.13
nezha	See advisory	2.0.13

Patched Releases

github.com/nezhahq/nezha

2.0.13

nezha

2.0.13

Timeline

Publicly disclosed
Jun 12, 2026
Last updated
Aug 12, 2026

Weakness Type

CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

References

FAQ

Common Questions.

Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool.
Affected: github.com/nezhahq/nezha (go); nezha. The full list is in the CVE brief.
It is not listed in any known-exploited vulnerabilities catalog.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
No public exploit code is known.
Fixed versions are available, including github.com/nezhahq/nezha 2.0.13, nezha 2.0.13.
Brandefense priority: patch in the next maintenance window, because of its high severity, although no exploitation is known.

Is CVE-2026-53519 Running On Your Attack Surface?

Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.