Credential exposure via unredacted list responses
Published Jul 10, 2026 · Updated Jul 10, 2026
Sensitive information exposure in Nezha Monitoring before 2.2.5 allows remote authenticated users to read third-party API credentials. The listDDNS and listNotification handlers copy full stored objects into API responses without redacting access secrets, webhook URLs, request headers, or bodies. An administrator session or PAT with the relevant read scope is required, and one request can disclose every stored integration credential visible to that principal.
Summary
What happened
Sensitive information exposure in Nezha Monitoring before 2.2.5 allows remote authenticated users to read third-party API credentials. The listDDNS and listNotification handlers copy full stored objects into API responses without redacting access secrets, webhook URLs, request headers, or bodies. An administrator session or PAT with the relevant read scope is required, and one request can disclose every stored integration credential visible to that principal.
The record
- CVE
- CVE-2026-59155
- Published
- Jul 10, 2026
- Updated
- Jul 10, 2026
- Vendor
- NezhaHQ
- Product
- Nezha Monitoring
- Classifications
- CWE-200, T1528
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 10, 2026CVE publishedPublication date reported by the CVE source.
- Jul 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.2.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Authenticated DDNS and notification list request PoCproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo