# CVE-2026-111387: Nezha information disclosure in DDNS API

Source: https://junglewise.ai/threats/cve-2026-111387-nezha-from-2-2-5-before-2-3-15-contains-an-information  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-16. Updated: 2026-10-16  
License: CC BY 4.0 with a link back

CVE-2026-111387 · Severity: medium · CVSS 6.5 · Published 2026-10-16

Nezha is a server monitoring and management platform used to collect system metrics and manage cloud infrastructure. The vulnerability allows authenticated users with specific permissions to retrieve plaintext third-party credentials—including API tokens and webhook secrets—from other users' DDNS (Dynamic DNS) profiles through an insufficiently redacted API endpoint, potentially exposing secrets used to manage DNS or trigger external integrations.

Technologies: [NezhaHQ Nezha](https://junglewise.ai/threats/technologies/nezha). Vendors: [NezhaHQ](https://junglewise.ai/threats/vendors/nezhahq).

## Quick answers

**Is CVE-2026-111387 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-111387 being exploited in the wild.

**How severe is CVE-2026-111387?** Medium severity, with a CVSS score of 6.5, published 16 October 2026.

**Which products and versions are affected?** NezhaHQ Nezha 2.2.5 through 2.3.14.

**Is there a fix for CVE-2026-111387?** Yes: fixed in 2.3.15. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-111387 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-111387?** Check whether you run NezhaHQ Nezha 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

- Fixed in 2.3.15

## Technical details

The GET /api/v1/ddns endpoint in Nezha 2.2.5 before 2.3.15 fails to redact sensitive credential fields (WebhookURL, WebhookRequestBody, AccessSecret, and Authorization headers) from list responses. An authenticated user with the nezha:ddns:read permission scope can call this endpoint to retrieve all DDNS profiles system-wide, exposing plaintext tokens and secrets embedded in webhook configurations and Cloudflare/TencentCloud API credentials. The vulnerability requires valid authentication and appropriate scopes but allows lateral disclosure of third-party credentials.

## Affected products

- nezhahq Nezha 2.2.5 through 2.3.14

## Timeline

- 2026-10-16: disclosed

## References

- [https://github.com/nezhahq/nezha/commit/36b742a7e9a81ed782363dd19efd77b7030fbd0f](https://github.com/nezhahq/nezha/commit/36b742a7e9a81ed782363dd19efd77b7030fbd0f)
- [https://github.com/nezhahq/nezha/commit/39d398066d8c644fe452f74704e34ada6c7ab61e](https://github.com/nezhahq/nezha/commit/39d398066d8c644fe452f74704e34ada6c7ab61e)

## Related threats

- [Nezha dashboard file manager WebSocket memory exhaustion](https://junglewise.ai/threats/cve-2026-111384-nezha-1-0-0-before-2-3-15-contains-a-memory-exhaustion)
- [Nezha Monitoring resource exhaustion via unbounded WebSocket streams](https://junglewise.ai/threats/cve-2026-53522-nezha-monitoring-resource-exhaustion-via-unbounded-websocket)
- [Nezha Monitoring Information Disclosure in Service Endpoints](https://junglewise.ai/threats/cve-2026-49397-nezha-monitoring-information-disclosure-in-service-endpoints)
- [Nezha Monitoring CSRF in cron manual-trigger endpoint](https://junglewise.ai/threats/cve-2026-49396-nezha-monitoring-csrf-in-cron-manual-trigger-endpoint)
- [Nezha Monitoring authorization bypass in service-monitor result worker](https://junglewise.ai/threats/cve-2026-48119-nezha-monitoring-authorization-bypass-in-service-monitor-result)