Skip to main content
Vulnerability Database/CVE-2026-111387

CVE-2026-111387: Nezha Information Disclosure Vulnerability

CVE-2026-111387 is an information disclosure vulnerability in Nezha versions 2.2.5 to 2.3.14 that exposes third-party credentials through unredacted webhook data. This article covers the technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-111387 Overview

CVE-2026-111387 is an information disclosure vulnerability in Nezha, an open-source server monitoring and management platform. Versions from 2.2.5 before 2.3.15 expose third-party credentials through the Dynamic DNS (DDNS) list endpoint. The listDDNS handler omits redaction of WebhookURL and WebhookRequestBody fields when returning DDNS profiles. Any authenticated administrator or Personal Access Token (PAT) with the nezha:ddns:read scope can call GET /api/v1/ddns and retrieve cleartext webhook tokens embedded in every user's DDNS profiles. The flaw is classified under [CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer].

Critical Impact

Authenticated attackers can harvest third-party DDNS provider credentials across all tenants, enabling account takeover of upstream DNS services.

Affected Products

  • Nezha versions 2.2.5 through 2.3.14
  • Dashboard component cmd/dashboard/controller/ddns.go
  • Related notification endpoint cmd/dashboard/controller/notification.go

Discovery Timeline

  • 2026-10-16 - CVE-2026-111387 published to NVD
  • 2026-10-16 - Last updated in NVD database

Technical Details for CVE-2026-111387

Vulnerability Analysis

The vulnerability resides in the Nezha dashboard's DDNS list controller. When returning a list of DDNS profiles, the handler creates a copy of the in-memory profiles using copier.Copy and zeroes out AccessSecret and WebhookHeaders. However, the handler fails to redact the WebhookURL and WebhookRequestBody fields. These fields commonly contain bearer tokens, API keys, or signed URL parameters used to authenticate webhook calls to DDNS providers.

Because the Nezha dashboard is multi-tenant, a single authenticated administrator or any PAT scoped to nezha:ddns:read can enumerate credentials belonging to every user on the instance. Harvested tokens can be reused to manipulate DNS records at the upstream provider, redirecting traffic or facilitating phishing.

Root Cause

The root cause is incomplete sanitization of a response data transfer object. The patch in commit 39d3980 added partial redaction, and the follow-up commit 36b742a extended that redaction to cover WebhookURL and WebhookRequestBody. The underlying design flaw is reliance on field-by-field blocklisting rather than an allowlist of safe fields for list responses.

Attack Vector

Exploitation requires network access to the Nezha dashboard API and valid credentials with the nezha:ddns:read scope. The attacker issues a single GET /api/v1/ddns request and parses the JSON response. No user interaction, timing, or special payload is required.

go
// Security patch in cmd/dashboard/controller/ddns.go
// commit 36b742a7e9a81ed782363dd19efd77b7030fbd0f
// 不影响 singleton 内原始数据。
for _, p := range ddnsProfiles {
    p.AccessSecret = ""
    p.WebhookURL = ""         // added by patch
    p.WebhookRequestBody = "" // added by patch
    p.WebhookHeaders = ""
}

Source: GitHub commit 36b742a

Detection Methods for CVE-2026-111387

Indicators of Compromise

  • Unexpected GET /api/v1/ddns requests from administrative sessions or PATs, especially from new IP addresses or user agents.
  • Dashboard access logs showing repeated listDDNS calls followed by outbound traffic to DDNS provider APIs.
  • Rotation events or anomalous authentication failures at upstream DDNS providers following dashboard access.

Detection Strategies

  • Review Nezha access logs for calls to /api/v1/ddns and correlate with the authenticating user or PAT scope.
  • Audit all active PATs for the nezha:ddns:read scope and flag tokens held by non-administrative users.
  • Compare webhook secret values against known-good baselines; treat any disclosure to a non-owner as a credential compromise.

Monitoring Recommendations

  • Forward Nezha dashboard HTTP access logs to a centralized logging platform for query and retention.
  • Alert on anomalous enumeration patterns against /api/v1/* endpoints by individual accounts.
  • Monitor DDNS provider audit logs for authentication from unexpected source addresses after dashboard access.

How to Mitigate CVE-2026-111387

Immediate Actions Required

  • Upgrade Nezha to version 2.3.15 or later immediately.
  • Rotate all DDNS webhook secrets, URLs with embedded tokens, and request body credentials configured in Nezha.
  • Revoke and reissue any PAT that holds the nezha:ddns:read scope and re-scope strictly to intended operators.
  • Audit DDNS provider account activity for unauthorized record changes since the vulnerable version was deployed.

Patch Information

The fix is distributed in Nezha 2.3.15. Two commits address the issue: commit 39d3980 introduces redaction of AccessSecret and WebhookHeaders in the list endpoint, and commit 36b742a extends the redaction to WebhookURL and WebhookRequestBody. Refer to GitHub Security Advisory GHSA-hpfr-cmgc-f455 and the VulnCheck Advisory for complete remediation guidance.

Workarounds

  • Restrict dashboard network exposure to trusted administrative networks until the patch is applied.
  • Remove or null out WebhookURL and WebhookRequestBody fields for existing DDNS profiles if upgrade is delayed.
  • Temporarily revoke all PATs carrying the nezha:ddns:read scope.
bash
# Upgrade example for Docker Compose deployments
docker compose pull
docker compose up -d
# Verify the running version is 2.3.15 or later
docker exec nezha-dashboard /dashboard-linux-amd64 --version

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.