dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-47124

MEDIUM · 6.5 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 →
71/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 1.4.0 to before version 2.0.9, any authenticated non-admin member can connect to the server-status WebSocket and receive telemetry for all servers, including servers owned by other users. The normal server list API filters objects by HasPermission, but the WebSocket stream treats the presence of any authenticated user as authorization for the full unfiltered server list. This issue has been patched in version 2.0.9.

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.8 contain a broken access control vulnerability in the server-status WebSocket endpoint. While the REST API correctly filters server objects by HasPermission, the WebSocket stream incorrectly treats any authenticated user as authorized for the full unfiltered server list, allowing non-admin users to view telemetry data for servers they do not own.

MitigationUpgrade to Nezha Monitoring version 2.0.9 or later, which includes the patch for this authorization flaw.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Check Nezha Monitoring version
    View the installed version in the dashboard (Settings > About) or run 'nezha-agent --version' on the server
    Affected if Version is between 1.4.0 and 2.0.8 inclusive
  2. Verify non-admin users exist
    Log into the Nezha dashboard and check Settings > User Management for accounts with non-admin roles
    Affected if More than one user account exists with a role other than administrator
  3. Test WebSocket server-status endpoint authorization
    Using a non-admin user account, establish a WebSocket connection to the server-status endpoint (typically /api/v1/ws/server-status or /ws/server-status) and observe the server list returned
    Affected if The WebSocket response contains telemetry data for servers that the authenticated user does not own or is not assigned to
  4. Compare REST API vs WebSocket server list
    As a non-admin user, request the server list via the REST API (GET /api/v1/servers) and compare it against the server list received via the WebSocket connection
    Affected if The WebSocket returns more servers than the REST API, indicating unfiltered data
  5. Check if server-status WebSocket is publicly accessible
    Review the Nezha server configuration and firewall rules to determine if the WebSocket endpoint is exposed to untrusted networks
    Affected if The WebSocket endpoint is accessible from networks outside the trusted administrative zone

If Nezha Monitoring version 1.4.0 through 2.0.8 is running and non-admin users can access the server-status WebSocket endpoint to view servers they do not own, the environment is affected by this vulnerability

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.9 or later, which includes the patch for this authorization flaw.

Recommended fix High confidence

2.0.9

  1. 1. Backup your current Nezha Monitoring installation and database
  2. 2. Identify your current version by checking the running container or binary version
  3. 3. Stop the Nezha Monitoring service
  4. 4. Upgrade to version 2.0.9 or later (e.g., pull the latest Docker image or download the new release binary)
  5. 5. Start the Nezha Monitoring service
  6. 6. Verify the WebSocket endpoint now properly filters server data based on user permissions
  7. 7. Confirm that non-admin users can only access their own servers via the server-status WebSocket

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-47124 — 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-47124 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