CVE-2026-59155

Nezha Monitoring: DDNS and Notification credential exposure via unredacted list API

MEDIUM
6.9
CVSS Score
Published: July 10, 2026 at 09:31 PM UTC
Updated: October 25, 2026 at 03:10 PM UTC
1 product affected across 1 vendorNezha

Using nezha by nezhahq?

Get instant alerts when new vulnerabilities affect nezha - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.9
Exploit prediction
EPSS 0.4%
SSVC
PoC

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2.2.5
Affected range stops below 2.2.5, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.9MEDIUMGitHub_M
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-200

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card