CVE-2026-47268: CWE-918: Server-Side Request Forgery (SSRF) in nezhahq nezha
Nezha Monitoring versions from 0.20.0 up to but not including 2.0.10 contain a server-side request forgery (SSRF) vulnerability. An authenticated dashboard user can configure a DDNS profile with arbitrary webhook parameters, causing the dashboard to send crafted HTTP requests to internal or loopback network services without SSRF protections. The response is not returned to the attacker, resulting in a blind SSRF that can change internal state. This vulnerability was patched in version 2.0.10.
AI Analysis
Technical Summary
CVE-2026-47268 is a server-side request forgery vulnerability in Nezha Monitoring, affecting versions >=0.20.0 and <2.0.10. Authenticated users with dashboard access can create or update DDNS profiles to specify arbitrary webhook URLs, HTTP methods, request bodies, and headers. When the DDNS triggers, the dashboard sends these requests using utils.HttpClient without the SSRF protections applied to notification webhooks. This allows low-privileged users to induce the dashboard host to make HTTP requests to internal or loopback network services. The attack is blind as the response body is not returned to the attacker, but it can cause internal state changes. The issue is fixed in version 2.0.10.
Potential Impact
An authenticated low-privileged user can leverage this SSRF vulnerability to make the Nezha dashboard server send arbitrary HTTP requests to internal or loopback network services. This can lead to unauthorized internal network interactions and potential state changes within internal services. Confidentiality and integrity impacts are limited to partial information disclosure and internal state modification, respectively. Availability is not affected. The CVSS score is 6.4 (medium severity).
Mitigation Recommendations
This vulnerability is fixed in Nezha Monitoring version 2.0.10. Users should upgrade to version 2.0.10 or later to remediate this issue. No official temporary fixes or workarounds are documented. Since this is a self-hosted product, patching is the recommended mitigation.
CVE-2026-47268: CWE-918: Server-Side Request Forgery (SSRF) in nezhahq nezha
Description
Nezha Monitoring versions from 0.20.0 up to but not including 2.0.10 contain a server-side request forgery (SSRF) vulnerability. An authenticated dashboard user can configure a DDNS profile with arbitrary webhook parameters, causing the dashboard to send crafted HTTP requests to internal or loopback network services without SSRF protections. The response is not returned to the attacker, resulting in a blind SSRF that can change internal state. This vulnerability was patched in version 2.0.10.
CVSS v3.1
Score 6.4medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-47268 is a server-side request forgery vulnerability in Nezha Monitoring, affecting versions >=0.20.0 and <2.0.10. Authenticated users with dashboard access can create or update DDNS profiles to specify arbitrary webhook URLs, HTTP methods, request bodies, and headers. When the DDNS triggers, the dashboard sends these requests using utils.HttpClient without the SSRF protections applied to notification webhooks. This allows low-privileged users to induce the dashboard host to make HTTP requests to internal or loopback network services. The attack is blind as the response body is not returned to the attacker, but it can cause internal state changes. The issue is fixed in version 2.0.10.
Potential Impact
An authenticated low-privileged user can leverage this SSRF vulnerability to make the Nezha dashboard server send arbitrary HTTP requests to internal or loopback network services. This can lead to unauthorized internal network interactions and potential state changes within internal services. Confidentiality and integrity impacts are limited to partial information disclosure and internal state modification, respectively. Availability is not affected. The CVSS score is 6.4 (medium severity).
Mitigation Recommendations
This vulnerability is fixed in Nezha Monitoring version 2.0.10. Users should upgrade to version 2.0.10 or later to remediate this issue. No official temporary fixes or workarounds are documented. Since this is a self-hosted product, patching is the recommended mitigation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-18T23:03:37.229Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a2c7c90e617e2d834c6c7af
Added to database: 6/12/2026, 9:39:28 PM
Last enriched: 6/12/2026, 9:55:35 PM
Last updated: 6/13/2026, 5:57:17 AM
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.