CVE-2026-46716
RCE via cross-tenant cron task in Nezha Monitoring before v2.0.8
Is CVE-2026-46716 being exploited?
Not confirmed. CVE-2026-46716 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.43% probability of exploitation in the next 30 days.
How severe is CVE-2026-46716?
CVE-2026-46716 is rated Critical with a CVSS score of 9.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-46716?
Yes. A fix has been recorded for CVE-2026-46716. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-46716 affect?
CVE-2026-46716 affects Nezha Monitoring (versions 1.4.0–2.0.7). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-46716?
Upgrade to v2.0.8+; audit cron tasks; rotate credentials.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution across tenants via shared cron; attacker executes commands and exfiltrates output to a webhook.
Patch when possible
- affected>= 1.4.0 and < 2.0.8
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.