CVE-2026-49396: Nezha Monitoring CSRF in cron manual-trigger endpoint

CVE-2026-49396 · Severity: high · CVSS 7.1 · Published 2026-06-12

Nezha Monitoring is a tool used to manage and monitor servers and websites. A security flaw allows an attacker to trick a logged-in administrator into unintentionally running pre-configured maintenance commands on their monitored servers. While the attacker cannot create new commands, they can force the execution of existing ones, which could lead to unauthorized system changes or service disruptions.

Technologies: github.com/nezhahq/nezha (Go), NezhaHQ Nezha. Vendors: Go, NezhaHQ.

Quick answers

Is CVE-2026-49396 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-49396 being exploited in the wild.
How severe is CVE-2026-49396?
High severity, with a CVSS score of 7.1, published 12 June 2026.
Which products and versions are affected?
github.com/nezhahq/nezha (Go) >= 1.0.0, < 2.0.14, SEMVER:introduced=1.0.0, SEMVER:introduced=1.0.0,fixed=2.0.14; NezhaHQ Nezha >= 1.0.0, < 2.0.14; NezhaHQ Nezha Monitoring >= 1.0.0, < 2.0.14.
Is there a fix for CVE-2026-49396?
Yes. github.com/nezhahq/nezha (Go): upgrade to 2.0.14 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-49396 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-49396?
Check whether you run github.com/nezhahq/nezha (Go), NezhaHQ Nezha or NezhaHQ Nezha Monitoring at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/nezhahq/nezha (Go): upgrade to 2.0.14 or later
    go get github.com/nezhahq/nezha@v2.0.14

Technical details

A Cross-Site Request Forgery (CSRF) vulnerability exists in the Nezha Monitoring dashboard due to the use of a state-changing GET endpoint for manual cron execution. The endpoint `/api/v1/cron/:id/manual` is authenticated via a JWT stored in a cookie with `SameSite=Lax` configuration. Because browsers include Lax cookies on top-level cross-site GET navigations and the endpoint lacks CSRF tokens or Origin/Fetch Metadata validation, an attacker can induce a logged-in user to trigger existing cron tasks. An exploit results in the dispatch of stored commands to connected agents. The vulnerability is patched in version 2.0.14.

Affected products

  • NezhaHQ Nezha Monitoring >= 1.0.0, < 2.0.14

Identifiers

  • CVE-2026-49396
  • GHSA-8qhj-4f8c-j8qg
  • GO-2026-5261

Timeline

  • 2026-05-26: advisory: GitHub Security Advisory published
  • 2026-06-12: disclosed: CVE published to NVD
  • 2026-06-12: patched: Fix released in version 2.0.14

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.