CVE-2026-49397
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 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.
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 · high confidenceNezha Monitoring versions 2.0.0 through 2.0.13 expose private services (those with EnableShowInService: false) through per-server API endpoints, allowing unauthenticated enumeration of service names and timing data that should be hidden.
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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
-
Identify Nezha Monitoring installationCheck for Nezha Monitoring by looking for the executable or service. Common locations include /opt/nezha, /usr/local/nezha, or check running processes with 'ps aux | grep nezha' or 'systemctl list-units | grep nezha'Affected if Nezha Monitoring process or service is found running on the system
-
Determine installed Nezha versionRun 'nezha --version' or check the version file if present in the installation directory. Alternatively, check the Docker container tag if running via DockerAffected if Installed version is 2.0.0 through 2.0.13 inclusive
-
Verify private services existExamine the Nezha configuration for services with EnableShowInService: false setting, typically found in the dashboard configuration or YAML configuration files under the services sectionAffected if Configuration contains one or more services with EnableShowInService set to false
-
Check API endpoint accessibilityAttempt to access the per-server API endpoints (typically /api/v1/server/<server_id>/services or similar) without authentication to see if private service information is returnedAffected if API endpoints return private service names or timing data without requiring authentication when EnableShowInService is false
You are affected if Nezha Monitoring versions 2.0.0-2.0.13 are running and private services with EnableShowInService: false exist, as these can be enumerated via unauthenticated API endpoints.
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 Nezha Monitoring to version 2.0.14 or later to patch the information disclosure vulnerability.
Version 2.0.14
- 1. Identify the current version of Nezha Monitoring installation by checking the application or deployment documentation
- 2. If running a version between 2.0.0 and 2.0.13 inclusive, plan for upgrade
- 3. Back up current configuration and data before upgrading
- 4. Upgrade Nezha Monitoring to version 2.0.14 or later release
- 5. After upgrade, verify that private services with EnableShowInService: false are no longer accessible via per-server endpoints
- 6. Test that monitoring functionality continues to work as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49397 — 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-49397 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