CVE-2026-49396
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 · uneditedNezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool. From version 1.0.0 to before version 2.0.14, cross-site GET request can trigger stored cron commands on a victim's agents. This issue has been patched in version 2.0.14.
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 confidenceNezha Monitoring versions 1.0.0 through 2.0.13 contain a stored Cross-Site Request Forgery (CSRF) vulnerability. Attackers can trigger pre-configured cron commands on victim agents by诱导受害者访问恶意URL或点击链接执行跨站GET请求，从而激活已存储的定时任务。
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Check Nezha Monitoring versionAccess the Nezha dashboard and navigate to the settings or about page to view the installed version. Alternatively, check the Docker container or installation logs for the version number.Affected if The installed version falls between 1.0.0 and 2.0.13 inclusive.
-
Identify configured cron or scheduled tasksIn the Nezha dashboard, go to the scheduled task or cron job configuration section. List all active scheduled tasks that are configured to run on agent machines.Affected if There are scheduled tasks configured to execute commands on agents.
-
Check dashboard accessibilityVerify if the Nezha dashboard web interface is accessible from untrusted networks or the internet without proper network segmentation or authentication barriers.Affected if The dashboard is exposed to untrusted networks where attackers could potentially send cross-site requests.
-
Review recent task execution logsExamine the Nezha agent or dashboard logs for any scheduled task executions that occurred without legitimate administrative action, looking for unexpected cron triggers.Affected if There are scheduled task executions that cannot be attributed to authorized administrative actions.
You are affected if Nezha Monitoring version 2.0.13 or earlier is running, the dashboard web interface is accessible, and scheduled cron tasks are configured that could be triggered via CSRF requests.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to Nezha Monitoring version 2.0.14 or later which contains the security patch for this CSRF vulnerability.
2.0.14
- Check current Nezha Monitoring version (e.g., via dashboard or command line)
- If version is 1.0.0 or higher but below 2.0.14, upgrade to version 2.0.14 or later
- Verify the upgrade was successful by checking the version number after update
- Confirm that cron command functionality still works as expected after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49396 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-49396 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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