dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-47268

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool. From version 0.20.0 to before version 2.0.10, an authenticated Nezha dashboard user can create or update a DDNS profile with provider webhook and configure an arbitrary webhook_url, HTTP method, request body, and headers. When DDNS is triggered for a server that uses that profile, the dashboard process sends the configured request with utils.HttpClient without the SSRF protections used by notification webhooks. This allows a low-privileged authenticated user who controls an owned server/DDNS profile to make the dashboard host issue HTTP requests to loopback or internal network services. The response body is not returned to the attacker in the confirmed path, so this is a blind SSRF / internal state-changing request primitive. This issue has been patched in version 2.0.10.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Authenticated Nezha dashboard users can configure DDNS profiles with arbitrary webhooks (URL, method, body, headers) that bypass SSRF protections present in notification webhooks. When DDNS triggers for a server using such a profile, the dashboard issues HTTP requests to attacker-controlled URLs, including internal/loopback addresses. This is a blind SSRF since the response is not returned to the attacker.

MitigationUpgrade to Nezha Monitoring version 2.0.10 or later, which includes SSRF protection for DDNS webhook requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Nezha Monitoring installation and version
    Check the running Nezha dashboard version - typically via the UI footer, Docker container tag, or binary version flag (e.g., `nezha-agent --version` or checking the dashboard /api/version endpoint)
    Affected if The installed version is prior to 2.0.10 (the version that includes SSRF protection for DDNS webhooks)
  2. Verify DDNS feature is in use
    Examine the Nezha dashboard for configured DDNS profiles - navigate to the DDNS section or query the database/configuration for any profile definitions containing webhook configurations
    Affected if Any DDNS profiles exist with webhook configurations defined
  3. Inspect DDNS webhook URLs for internal/loopback targets
    Review each DDNS profile's webhook settings (URL, method, body, headers) and check if the URL field contains addresses such as 127.0.0.1, localhost, 192.168.x.x, 10.x.x.x, 172.16-31.x.x, or other RFC1918 private addresses
    Affected if Any DDNS webhook URL points to an internal network address or loopback interface (indicating exploitation of the SSRF vulnerability)
  4. Check for unexpected external webhook URLs
    Review all DDNS webhook URLs to identify any pointing to unusual or unauthorized external destinations that were not configured by an authorized administrator
    Affected if DDNS webhooks point to arbitrary external URLs that were not intentionally configured by the legitimate administrator

A user is affected if Nezha Monitoring version is below 2.0.10 AND DDNS profiles with webhooks are configured, particularly if any webhook URLs target internal/loopback addresses or unauthorized external endpoints.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Nezha Monitoring version 2.0.10 or later, which includes SSRF protection for DDNS webhook requests.

Recommended fix High confidence

2.0.10

  1. Upgrade Nezha Monitoring to version 2.0.10 or later

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47268 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47268 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data