dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-46717

HIGH · 7.7 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 →
83/100
Remediation priority · High
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 1.4.0 to before version 2.0.8, nezha's dashboard supports two user roles: RoleAdmin (Role==0) and RoleMember (Role==1). The notification routes POST /api/v1/notification and PATCH /api/v1/notification/:id are wired through commonHandler rather than adminHandler — so a RoleMember user can call them. These handlers synchronously Send() an HTTP request to a user-controlled URL and reflect the entire response body (no size limit) back to the caller on any non-2xx response. This issue has been patched in version 2.0.8.

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

Nezha Monitoring versions 1.4.0 through 2.0.7 have an improper access control vulnerability where notification API endpoints (POST /api/v1/notification and PATCH /api/v1/notification/:id) are routed through commonHandler instead of adminHandler, allowing RoleMember (non-admin) users to access admin-level functionality. Additionally, these handlers synchronously send HTTP requests to user-controlled URLs and reflect the full response body (no size limit) back to the caller on any non-2xx response, enabling potential SSRF or response smuggling attacks.

MitigationUpgrade to Nezha Monitoring version 2.0.8 or later, which patches this vulnerability by routing the notification endpoints through the proper adminHandler.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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
    Locate the Nezha Monitoring service binary or container and determine its version using --version flag, docker image tag, or package manager information. Compare this version against the affected range 1.4.0 through 2.0.7.
    Affected if The installed version falls within 1.4.0 to 2.0.7 inclusive.
  2. Verify API endpoint routing for notification endpoints
    Examine the application source code or configuration to confirm whether POST /api/v1/notification and PATCH /api/v1/notification/:id are routed through commonHandler rather than adminHandler. This typically requires code review or API introspection.
    Affected if The notification endpoints are handled by commonHandler instead of the admin-exclusive handler.
  3. Test access control on affected endpoints
    Authenticate as a non-admin user (RoleMember) and attempt to send POST or PATCH requests to /api/v1/notification endpoints. Observe whether the requests are accepted or rejected.
    Affected if Non-admin users (RoleMember) can successfully access and modify notification settings through these endpoints.
  4. Check for user-controlled URL handling in notification feature
    As a non-admin user, configure a notification with an attacker-controlled URL and trigger a notification send. Observe whether the application makes synchronous HTTP requests to arbitrary URLs.
    Affected if The notification feature allows non-admin users to specify arbitrary URLs for HTTP requests.
  5. Verify response reflection behavior
    Configure a notification URL that returns a large or malformed HTTP response. Trigger the notification and check whether the full response body is reflected back to the caller without size limits.
    Affected if Non-2xx responses from arbitrary URLs are reflected in full back to the caller without size limitation.

You are affected if running Nezha Monitoring version 1.4.0 through 2.0.7 and non-admin (RoleMember) users can access or modify notification settings via the API 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.8 or later, which patches this vulnerability by routing the notification endpoints through the proper adminHandler.

Recommended fix High confidence

2.0.8

  1. 1. Identify the current version of Nezha Monitoring installation (check via dashboard or CLI command like `nezha --version` or review docker image tag)
  2. 2. If the current version is 1.4.0 through 2.0.7 (inclusive), the installation is vulnerable
  3. 3. Upgrade to version 2.0.8 or later by pulling the updated container image or binary
  4. 4. After upgrade, verify the fix by confirming that RoleMember users can no longer access POST /api/v1/notification and PATCH /api/v1/notification/:id endpoints

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46717 — 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-46717 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