CVE-2026-48119
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 0.20.0 to before version 2.0.12, authenticated agents can forge service-monitor results for other users' services. This issue has been patched in version 2.0.12.
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 0.20.0 through 2.0.11 have a broken access control vulnerability where authenticated agents can submit forged service-monitor results for other users' services. This allows a compromised or malicious agent to falsify monitoring data for services they do not own.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.
-
Identify Nezha Monitoring installationLocate the Nezha Monitoring server installation and identify the running version. Common methods: check the web UI footer for version number, run 'nezha --version' from the server command line, or check the Docker image tag if running containerized.Affected if Running version is between 0.20.0 and 2.0.11 inclusive
-
Verify service-monitor feature is activeCheck the Nezha Monitoring configuration or web UI to determine if the service-monitor or monitoring agents feature is enabled. Look for any configured service monitors or agent deployments.Affected if Service-monitor functionality is enabled and agents are configured to report monitoring data
-
Review agent authentication configurationExamine the agent configuration files and server settings to see how agents authenticate. Check if agents use shared secrets or per-agent tokens, and whether agent identifiers can be spoofed.Affected if Agents authenticate with weak or shared credentials that could be replayed or forged
-
Audit existing monitoring data ownershipReview the monitoring dashboard or database to identify which agents are submitting data for which services. Look for mismatches where an agent reports on services outside its expected scope.
You are affected if Nezha Monitoring version 2.0.11 or earlier is running AND the service-monitor feature is enabled, allowing agents to submit monitoring data.
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.12 or later. Review agent access controls and audit existing monitoring data for signs of tampering until the patch is applied.
2.0.12
- Backup your current Nezha Monitoring installation and database before proceeding
- Upgrade Nezha Monitoring to version 2.0.12 or later
- After upgrade, verify that agents can no longer forge service-monitor results for other users' services
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48119 — 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-48119 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