CVE-2026-59155 Nezha Monitoring: DDNS and Notification credential exposure via unredacted list API
Authenticated users can retrieve plaintext third-party API credentials from monitoring endpoints due to missing redaction in Nezha Monitoring.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-59155?
CVE-2026-59155 is a medium-severity vulnerability in nezhahq nezha, published on 10 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool. Prior to 2.2.5, the GET /api/v1/ddns and GET /api/v1/notification endpoints return full resource objects including plaintext third-party API credentials, including Cloudflare API tokens, TencentCloud SecretKeys, Slack, Discord, and Telegram webhook URLs with embedded bot tokens, and Authorization header values, without any field-level redaction. Any authenticated admin or PAT with nezha:ddns:read or nezha:notification:read scope can receive stored credentials through the listDDNS and listNotification handlers in a single API response. This issue is fixed in version 2.2.5.
Weakness: CWE-200
Which versions are affected by CVE-2026-59155?
3 open source packages ship an affected version, including github.com/nezhahq/nezha.
| Package | Affected | Fixed in |
|---|---|---|
github.com/nezhahq/nezha Go | All versions | None |
github.com/nezhahq/nezha Go | All versions | 2.2.5 |
github.com/nezhahq/nezha Go | All versions | 2.2.5 |
How do I fix CVE-2026-59155?
Upgrade github.com/nezhahq/nezha to 2.2.5 or later.
Is CVE-2026-59155 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59155 exists.
Sources
Also known as GHSA-ww5p-j6cj-6mqq, GO-2026-5832.