Nezha Monitoring: Pre-auth path traversal via /dashboard.. prefix confusion leaks jwt_secret_key
48Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 9.1epss 0.5%
from disclosure to weapon3 days
Published on NVDJun 12
1st PoC+3d
exploitation probability
0.5%top 58% of all CVEs
observed exploitation
nono source reports it
1 public exploit(s)
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:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Affected products
nezhahq · nezhapublic PoCs found — 1
githubgithub.com/tar-xz/CVE-2026-53519-PoC★ 3⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.