Is CVE-2026-48119 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-48119 being exploited in the wild.

How severe is CVE-2026-48119?

High severity, with a CVSS score of 7.1, published 12 June 2026.

Which products and versions are affected?

github.com/naiba/nezha (Go) SEMVER:introduced=0.20.0; github.com/nezhahq/nezha (Go) SEMVER:introduced=0.20.0,fixed=1.14.15-0.20260521020202-02129f16fb15, SEMVER:introduced=1.0.0,fixed=1.14.15-0.20260521020202-02129f16fb15; NezhaHQ Nezha >= 0.20.0, = 2.0.0, < 2.0.12; NezhaHQ Nezha Monitoring 0.20.0 to 2.0.11.

Is there a fix for CVE-2026-48119?

Yes. github.com/nezhahq/nezha (Go): upgrade to 1.14.15-0.20260521020202-02129f16fb15 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-48119 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-48119?

Check whether you run github.com/naiba/nezha (Go), github.com/nezhahq/nezha (Go), NezhaHQ Nezha or one of the others listed 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.

CVE-2026-48119: Nezha Monitoring authorization bypass in service-monitor result worker

Q: Is there a fix for CVE-2026-48119?

Yes. github.com/nezhahq/nezha (Go): upgrade to 1.14.15-0.20260521020202-02129f16fb15 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-48119 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-48119?

Check whether you run github.com/naiba/nezha (Go), github.com/nezhahq/nezha (Go), NezhaHQ Nezha or one of the others listed 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.

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

Nezha Monitoring is a self-hosted tool used for monitoring the health and performance of servers and websites. A security flaw allows a user with valid agent credentials to submit fake monitoring data for services they do not own. This could lead to inaccurate status reports, false alerts, and the corruption of historical monitoring data, potentially causing operational confusion or masking actual service outages.

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

Quick answers

Is CVE-2026-48119 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-48119 being exploited in the wild.
How severe is CVE-2026-48119?: High severity, with a CVSS score of 7.1, published 12 June 2026.
Which products and versions are affected?: github.com/naiba/nezha (Go) SEMVER:introduced=0.20.0; github.com/nezhahq/nezha (Go) SEMVER:introduced=0.20.0,fixed=1.14.15-0.20260521020202-02129f16fb15, SEMVER:introduced=1.0.0,fixed=1.14.15-0.20260521020202-02129f16fb15; NezhaHQ Nezha >= 0.20.0, < 1.14.15-0.20260521020202-02129f16fb15; >= 2.0.0, < 2.0.12; NezhaHQ Nezha Monitoring 0.20.0 to 2.0.11.
Is there a fix for CVE-2026-48119?: Yes. github.com/nezhahq/nezha (Go): upgrade to 1.14.15-0.20260521020202-02129f16fb15 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-48119 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-48119?: Check whether you run github.com/naiba/nezha (Go), github.com/nezhahq/nezha (Go), NezhaHQ Nezha or one of the others listed 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 1.14.15-0.20260521020202-02129f16fb15 or later
```
go get github.com/nezhahq/nezha@v1.14.15-0.20260521020202-02129f16fb15
```

Technical details

A missing authorization check in the service-monitor result worker (specifically within `service/singleton/servicesentinel.go`) allows authenticated agents to submit `TaskResult` messages for any service ID. While the dashboard correctly restricts outbound task dispatch based on server ownership and service coverage, the inbound gRPC stream processing only verifies that the reported service ID exists. It fails to validate that the reporting agent was actually assigned the task or that the agent's owner has permission to monitor that specific service. An attacker with a valid agent secret can exploit this to inject arbitrary monitoring data, including 'successful' or 'failed' states and custom result text, into the history and current status of victim-owned services. This vulnerability was patched in version 2.0.12.

Affected products

NezhaHQ Nezha Monitoring 0.20.0 to 2.0.11

Identifiers

CVE-2026-48119
GHSA-4g6j-g789-rghm
GO-2026-5119

Timeline

2026-05-21: advisory: Original GitHub Security Advisory published
2026-06-12: disclosed: CVE published to NVD
2026-06-12: patched: Patch confirmed in version 2.0.12

References

https://github.com/nezhahq/nezha/security/advisories/GHSA-4g6j-g789-rghm

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