CVE-2026-53521

MEDIUMPre-NVD 6.46.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 87% 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
6.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.4Exploit: NoneExposed: 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. From version 2.0.14 to before version 2.1.0, PATCH /server/{id} accepts and persists nonexistent ddns_profiles IDs for a member-owned server. If another user later creates a DDNS profile with one of those IDs, the DDNS worker resolves the stored ID and dispatches an update using the other user's DDNS profile configuration in the context of the attacker's server. This issue has been patched in version 2.1.0.

CVSS v3
6.4
EG Score
6.4(medium)
EPSS
13.4%
KEV
Not listed

Published

June 12, 2026

Last Modified

June 15, 2026

Advisory Details (1)

Auto-updated Jun 13, 2026
Patch available. Sources: github.
github Patch Available

Stored future DDNS profile ID allows unauthorized use of another user's DDNS profile context · Advisory · nezhahq/nezha · GitHub

https://github.com/nezhahq/nezha/security/advisories/GHSA-39g2-8x68-pmx8

Vendor Advisories for CVE-2026-53521(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 63× 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.

  1. 2026-07-07 00:55 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 09:36 UTCEG score recompute
  7. 2026-07-05 02:31 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 10:22 UTCEG score recompute
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-03 08:09 UTCEG score recompute
  13. 2026-07-02 09:47 UTCEG score recompute
  14. 2026-07-01 15:07 UTCEPSS rescore
  15. 2026-07-01 11:33 UTCEG score recompute
  16. 2026-06-30 23:22 UTCEPSS rescore
  17. 2026-06-30 13:17 UTCEG score recompute
  18. 2026-06-29 14:54 UTCEG score recompute
  19. 2026-06-29 14:06 UTCEPSS rescore
  20. 2026-06-29 14:06 UTCEPSS rescore
  21. 2026-06-28 16:39 UTCEG score recompute
  22. 2026-06-28 14:07 UTCEPSS rescore
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-27 18:25 UTCEG score recompute
Show 38 more
  1. 2026-06-27 03:08 UTCEPSS rescore
  2. 2026-06-26 20:11 UTCEG score recompute
  3. 2026-06-25 21:57 UTCEG score recompute
  4. 2026-06-25 13:49 UTCEPSS rescore
  5. 2026-06-24 23:42 UTCEG score recompute
  6. 2026-06-24 14:05 UTCEPSS rescore
  7. 2026-06-24 01:28 UTCEG score recompute
  8. 2026-06-23 21:33 UTCEPSS rescore
  9. 2026-06-23 21:33 UTCEPSS rescore
  10. 2026-06-23 03:13 UTCEG score recompute
  11. 2026-06-22 14:25 UTCEPSS rescore
  12. 2026-06-22 14:25 UTCEPSS rescore
  13. 2026-06-22 04:52 UTCEG score recompute
  14. 2026-06-21 14:56 UTCEPSS rescore
  15. 2026-06-21 14:56 UTCEPSS rescore
  16. 2026-06-21 06:37 UTCEG score recompute
  17. 2026-06-21 01:59 UTCEPSS rescore
  18. 2026-06-21 01:59 UTCEPSS rescore
  19. 2026-06-20 08:20 UTCEG score recompute
  20. 2026-06-19 19:26 UTCEPSS rescore
  21. 2026-06-19 19:26 UTCEPSS rescore
  22. 2026-06-19 10:05 UTCEG score recompute
  23. 2026-06-18 17:52 UTCEPSS rescore
  24. 2026-06-18 17:52 UTCEPSS rescore
  25. 2026-06-18 11:48 UTCEG score recompute
  26. 2026-06-17 17:53 UTCEPSS rescore
  27. 2026-06-17 13:34 UTCEG score recompute
  28. 2026-06-16 17:53 UTCEPSS rescore
  29. 2026-06-16 15:19 UTCEG score recompute
  30. 2026-06-15 17:49 UTCEPSS rescore
  31. 2026-06-15 17:49 UTCEPSS rescore
  32. 2026-06-15 17:04 UTCEG score recompute
  33. 2026-06-14 23:18 UTCEPSS rescore
  34. 2026-06-14 18:46 UTCEG score recompute
  35. 2026-06-13 23:00 UTCEPSS rescore
  36. 2026-06-13 20:32 UTCEG score recompute
  37. 2026-06-12 22:18 UTCEG score recompute
  38. 2026-06-12 22:17 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53521?
CVE-2026-53521 is a medium vulnerability published on June 12, 2026. Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool. From version 2.0.14 to before version 2.1.0, PATCH /server/{id} accepts and persists nonexistent ddns_profiles IDs for a member-owned server. If another user later creates a DDNS profile with one of…
When was CVE-2026-53521 disclosed?
CVE-2026-53521 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-53521 actively exploited?
CVE-2026-53521 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 13.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53521?
CVE-2026-53521 has a CVSS v3 base score of 6.4 (NVD).
How do I remediate CVE-2026-53521?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53521, 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

Explore the affected products and dependency analysis for CVE-2026-53521

Explore →

Is Your Infrastructure Affected by CVE-2026-53521?

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

Start Free Scan →Browse All CVEs