CVE-2026-49396Public exploitNetwork attack vector

Forced agent command execution via state-changing GET

Published Jun 12, 2026 · Updated Jun 12, 2026

Cross-site request forgery in Nezha Monitoring 1.0.0 through 2.0.13 allows remote attackers to trigger stored commands on agents. The Dashboard's authenticated GET /api/v1/cron/:id/manual route changes state without a CSRF token, origin validation, or fetch-metadata check, while SameSite=Lax sends the victim's JWT cookie during top-level cross-site navigation. A logged-in Dashboard user must navigate to a crafted URL containing a known cron ID; the flaw only runs a command already stored and authorized for an online agent, but disruptive tasks can interrupt service.

CVSS severity7.1
High
EPSS probability0.12%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Cross-site request forgery in Nezha Monitoring 1.0.0 through 2.0.13 allows remote attackers to trigger stored commands on agents. The Dashboard's authenticated GET /api/v1/cron/:id/manual route changes state without a CSRF token, origin validation, or fetch-metadata check, while SameSite=Lax sends the victim's JWT cookie during top-level cross-site navigation. A logged-in Dashboard user must navigate to a crafted URL containing a known cron ID; the flaw only runs a command already stored and authorized for an online agent, but disruptive tasks can interrupt service.

The record

CVE
CVE-2026-49396
Published
Jun 12, 2026
Updated
Jun 12, 2026
Vendor
NezhaHQ
Product
Nezha Monitoring
Classifications
CWE-352, T1204.001
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jun 12, 2026CVE publishedPublication date reported by the CVE source.
  2. 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.

  1. Affected versionversion=>= 1.0.0, < 2.0.14

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

NezhaHQ · Nezha Monitoringversion=>= 1.0.0, < 2.0.14

Published CVSS scores

7.1GitHub, Inc.CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-352Cross-Site Request Forgery (CSRF)
T1204.001Malicious Link

Public exploit references

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