# CVE-2026-49397: Nezha's private services (`EnableShowInService: false`) are enumerable via per-server endpoints, leaking name and timing data

> Attackers can enumerate private monitoring services and leak their names and timing data via per-server endpoints in Nezha Monitoring.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-vrmh-5mmx-hjwx, GO-2026-5672

## What is CVE-2026-49397?

CVE-2026-49397 is a medium-severity vulnerability in nezhahq nezha, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool. From version 2.0.0 to before version 2.0.14, private services (`EnableShowInService: false`) are enumerable via per-server endpoints, leaking name and timing data. This issue has been patched in version 2.0.14.

Weakness: CWE-863 (Incorrect Authorization), CWE-285 (Improper Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-49397?

3 open source packages ship an affected version, including github.com/nezhahq/nezha.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/nezhahq/nezha` | Go | All versions | None |
| `github.com/nezhahq/nezha` | Go | From 2.0.0 | 2.0.14 |
| `github.com/nezhahq/nezha` | Go | From 2.0.0 | 2.0.14 |

## How do I fix CVE-2026-49397?

Upgrade github.com/nezhahq/nezha to 2.0.14 or later.

## Is CVE-2026-49397 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49397 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49397 and fix it if it is affected.

What it is: CVE-2026-49397 is a medium-severity vulnerability in nezhahq nezha, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49397 exists.

Affected packages and fixed versions:
- github.com/nezhahq/nezha (Go): affected all versions; no fix listed
- github.com/nezhahq/nezha (Go): affected from 2.0.0; fixed in 2.0.14
- github.com/nezhahq/nezha (Go): affected from 2.0.0; fixed in 2.0.14

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-49397/ (Markdown: https://insights.sbomify.com/CVE-2026-49397/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49397
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49397
- OSV: https://osv.dev/vulnerability/CVE-2026-49397

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-49397/
Summaries are generated and may contain mistakes; the official description above is the record.