Cross-tenant cron execution via unchecked trigger IDs
Published Jun 12, 2026 · Updated Jun 12, 2026
Missing authorization in Nezha Monitoring 1.4.0 through 2.0.7 allows remote authenticated users to trigger other users' cron tasks. The alert-rule and service create or update handlers accept FailTriggerTasks and RecoverTriggerTasks IDs but validate server maps rather than task ownership. RoleMember access and a pre-existing victim cron are required; when the selected alert or monitor trips, SendTriggerTasks executes the stored command on its configured servers.
Summary
What happened
Missing authorization in Nezha Monitoring 1.4.0 through 2.0.7 allows remote authenticated users to trigger other users' cron tasks. The alert-rule and service create or update handlers accept FailTriggerTasks and RecoverTriggerTasks IDs but validate server maps rather than task ownership. RoleMember access and a pre-existing victim cron are required; when the selected alert or monitor trips, SendTriggerTasks executes the stored command on its configured servers.
The record
- CVE
- CVE-2026-47120
- Published
- Jun 12, 2026
- Updated
- Jun 12, 2026
- Vendor
- NezhaHQ
- Product
- Nezha Monitoring
- Classifications
- CWE-863, CWE-862, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 12, 2026CVE publishedPublication date reported by the CVE source.
- Jun 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.4.0, < 2.0.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-rxf6-wjh4-jfj6 authenticated reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo