dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-46716

CRITICAL · 9.9 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 →
100/100
Remediation priority · Urgent
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, a RoleMember user can create a scheduled cron task with Cover=CronCoverAll, Servers=[] and an arbitrary Command. At every tick of the scheduler, the dashboard pushes that command to every server in the global ServerShared map — including servers that belong to other tenants (admin's servers, other members' servers). Each agent runs the command and returns the output, which is then sent to the attacker's own NotificationGroup → attacker-controlled webhook. 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

A low-privilege RoleMember user can create a scheduled cron task with Cover=CronCoverAll and empty Servers array that executes arbitrary commands on ALL servers in the global ServerShared map across all tenants. Command output is exfiltrated to the attacker's controlled webhook via a NotificationGroup.

MitigationUpgrade to version 2.0.8 or later immediately. As an interim measure, restrict or disable RoleMember scheduling permissions until patching is complete.

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

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

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 if cron scheduling feature is enabled
    Inspect system configuration files or database for scheduled task/cron functionality status. Look for settings like 'CronEnabled', 'TaskScheduling', or similar flags that control whether scheduled tasks can be created.
    Affected if Scheduling feature is enabled and RoleMember users have permission to create tasks
  2. Search for cron tasks with Cover=CronCoverAll and empty Servers array
    Query the scheduled tasks database or configuration for tasks where Cover is set to 'CronCoverAll' and Servers array is empty or null. This combination allows execution across all servers.
    Affected if Any cron task exists with Cover=CronCoverAll and empty Servers array
  3. Review NotificationGroups for external webhook URLs
    Examine all NotificationGroup configurations and identify any that point to external, attacker-controlled URLs. Check notification destinations for suspicious or unknown webhook endpoints.
    Affected if A NotificationGroup exists with a webhook URL pointing to an external domain not controlled by your organization
  4. Inspect global ServerShared map for multi-tenant exposure
    Review the ServerShared map configuration to confirm it contains servers from multiple tenants. Check if this map is accessible to low-privilege RoleMember users.
    Affected if ServerShared map contains servers across multiple tenants and is accessible to RoleMember users
  5. Verify RoleMember scheduling permissions
    Check role-based access control (RBAC) configuration to determine if RoleMember users have permissions to create or modify scheduled cron tasks.
    Affected if RoleMember role has scheduling or task creation permissions enabled

A user is affected if the scheduling feature is enabled, RoleMember users have task creation permissions, and any cron task exists with Cover=CronCoverAll and empty Servers array combined with a suspicious NotificationGroup pointing to an external webhook.

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 version 2.0.8 or later immediately. As an interim measure, restrict or disable RoleMember scheduling permissions until patching is complete.

Recommended fix High confidence

2.0.8

  1. 1. Back up your current Nezha Monitoring installation and database before proceeding with the upgrade.
  2. 2. If using Docker, stop the current container: docker-compose down or docker stop <container_id>
  3. 3. Pull the fixed version 2.0.8: docker pull nezhahq/nezha:v0.8.8 or git fetch && git checkout v0.8.8 for non-Docker installs
  4. 4. Restart the service with the new version: docker-compose up -d or your equivalent start command
  5. 5. Verify the upgrade was successful by checking the dashboard version number
Caveat Review release notes for 2.0.8 for any configuration changes; minor version upgrades typically do not introduce breaking changes

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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