dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-47120

HIGH · 7.1 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 →
77/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, a RoleMember can fire other users' cron tasks via AlertRule.FailTriggerTasks (no ownership check). 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 · moderate confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability where a RoleMember (non-admin user) can trigger other users' cron tasks through AlertRule.FailTriggerTasks due to a missing ownership verification check, allowing unauthorized manipulation of scheduled tasks.

MitigationUpgrade Nezha Monitoring to version 2.0.8 or later which includes the ownership check fix; verify that role-based access controls properly enforce task ownership boundaries.

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

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

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 version
    Run 'nezha-agent --version' or check the docker image tag/container version, or look in the application's about/settings page
    Affected if The installed version is below 2.0.8 (the fixed version)
  2. Determine user role configuration
    Check if there are non-admin RoleMember users defined in the system user management panel or by querying the users table for role='member' or role='user'
    Affected if Non-admin users (RoleMembers) exist in the system
  3. Verify AlertRule access for non-admins
    Attempt to access or enumerate AlertRule configurations through the API or web UI while logged in as a non-admin RoleMember user
    Affected if RoleMember users can view or modify AlertRule configurations that belong to other users
  4. Test FailTriggerTasks ownership boundary
    As a non-admin RoleMember, attempt to trigger a cron task associated with a different user by calling the AlertRule.FailTriggerTasks endpoint with another user's task ID
    Affected if The request succeeds and triggers the other user's scheduled task without ownership validation error
  5. Check API or application logs for authorization failures
    Review Nezha Monitoring application logs for 'FailTriggerTasks' entries and verify whether user ID ownership is being checked before task execution
    Affected if Logs show successful task triggers without ownership verification or show missing authorization checks

A user is affected if running Nezha Monitoring version below 2.0.8 and non-admin RoleMember users can trigger cron tasks belonging to other users through AlertRule.FailTriggerTasks without ownership validation.

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 Nezha Monitoring to version 2.0.8 or later which includes the ownership check fix; verify that role-based access controls properly enforce task ownership boundaries.

Recommended fix High confidence

Upgrade to version 2.0.8

  1. Identify your current Nezha Monitoring installation method (Docker, binary, or source)
  2. Backup your existing configuration and data directories
  3. For Docker deployments: Stop the container, pull the latest image with tag v2.0.8, and restart with your existing configuration
  4. For binary installations: Download the v2.0.8 release from the official repository, replace the binary, and restart the service
  5. For source installations: Pull the latest code, checkout tag v2.0.8, rebuild, and restart the service
  6. Verify the service starts successfully and check the version number confirms 2.0.8
  7. Test that RoleMember users can no longer trigger other users' cron tasks (the authorization check should now be in place)
Caveat Review release notes for any configuration changes between your current version and 2.0.8; minor version upgrades typically have low risk but always test in non-production first

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