Cross-user DDNS updates via unresolved profile IDs
Published Jun 12, 2026 · Updated Jun 12, 2026
Incorrect authorization in Nezha Monitoring 2.0.14 to before 2.1.0 allows remote authenticated users to trigger cross-user DDNS updates. The server update path persists nonexistent profile IDs, and the DDNS worker later resolves them without rechecking ownership. Exploitation requires a member-owned server and prediction or prebinding of a future ID; credentials remain server-side and DNS changes depend on provider permissions.
Summary
What happened
Incorrect authorization in Nezha Monitoring 2.0.14 to before 2.1.0 allows remote authenticated users to trigger cross-user DDNS updates. The server update path persists nonexistent profile IDs, and the DDNS worker later resolves them without rechecking ownership. Exploitation requires a member-owned server and prediction or prebinding of a future ID; credentials remain server-side and DNS changes depend on provider permissions.
The record
- CVE
- CVE-2026-53521
- Published
- Jun 12, 2026
- Updated
- Jun 12, 2026
- Vendor
- NezhaHQ
- Product
- Nezha Monitoring
- Classifications
- CWE-863, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 12, 2026CVE publishedPublication date reported by the CVE source.
- Jun 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 2.0.14, < 2.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- GHSA-39g2-8x68-pmx8 regression-test reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo