# 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.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 13 Jul 2026
- **Also known as:** GHSA-ww5p-j6cj-6mqq, GO-2026-5832

## 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 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-59155?

3 open source packages ship an affected version, including github.com/nezhahq/nezha.


| Package | Ecosystem | 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.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59155 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59155 exists.

Affected packages and fixed versions:
- github.com/nezhahq/nezha (Go): affected all versions; no fix listed
- github.com/nezhahq/nezha (Go): affected all versions; fixed in 2.2.5
- github.com/nezhahq/nezha (Go): affected all versions; fixed in 2.2.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-59155/ (Markdown: https://insights.sbomify.com/CVE-2026-59155/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59155
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59155
- OSV: https://osv.dev/vulnerability/CVE-2026-59155

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-59155/
Summaries are generated and may contain mistakes; the official description above is the record.
