CVE-2026-53521

See a problem?
Please try reporting it to the source first.
Source
https://cve.org/CVERecord?id=CVE-2026-53521
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53521.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-53521
Aliases
Downstream
Related
Published
2026-06-12T21:04:27.196Z
Modified
2026-08-12T03:51:21.280851306Z
Severity
  • 6.4 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:L CVSS Calculator
Summary
Nezha Monitoring: Stored future DDNS profile ID allows unauthorized use of another user's DDNS profile context
Details

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.

Database specific 
{
    "cna_assigner": "GitHub_M",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53521.json",
    "cwe_ids": [
        "CWE-863"
    ]
}
References

Affected packages

Git / github.com/nezhahq/nezha

Affected ranges

Type
GIT
Repo
https://github.com/nezhahq/nezha
Events
Introduced
8b5e382fe217107c7b777ea9c6b4bc3d2e156202
Fixed
1d70d2992ec7ee5fac2e12ce15d0ea8005a589d4
Database specific
Show details 
{
    "extracted_events": [
        {
            "introduced": "2.0.14"
        },
        {
            "fixed": "2.1.0"
        },
        {
            "introduced": "0"
        }
    ],
    "source": [
        "AFFECTED_FIELD",
        "DESCRIPTION"
    ]
}

Database specific

source 
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53521.json"