CVE-2026-59155: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in nezhahq nezha
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.
AI Analysis
Technical Summary
CVE-2026-59155 is an information exposure vulnerability in Nezha Monitoring (nezha) where API endpoints /api/v1/ddns and /api/v1/notification return full resource objects including plaintext sensitive credentials such as Cloudflare API tokens, TencentCloud SecretKeys, Slack, Discord, and Telegram webhook URLs with embedded bot tokens, and Authorization header values. This occurs for authenticated admins or personal access tokens with nezha:ddns:read or nezha:notification:read scopes. The issue affects versions prior to 2.2.5 and is resolved in 2.2.5.
Potential Impact
Sensitive third-party API credentials and authorization tokens are exposed to any authenticated user with specific read permissions, potentially allowing unauthorized access to integrated services. This exposure could lead to misuse of these credentials if an attacker gains the required access scope. However, exploitation requires authenticated access with elevated privileges.
Mitigation Recommendations
A fix is available in Nezha Monitoring version 2.2.5. Users should upgrade to version 2.2.5 or later to remediate this vulnerability. Since this is a self-hosted product, administrators must apply the update to their installations. The vendor manages remediation for the cloud service version. No additional mitigation steps are indicated in the advisory.
CVE-2026-59155: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in nezhahq nezha
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.
CVSS v4.0
Score 6.9medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-59155 is an information exposure vulnerability in Nezha Monitoring (nezha) where API endpoints /api/v1/ddns and /api/v1/notification return full resource objects including plaintext sensitive credentials such as Cloudflare API tokens, TencentCloud SecretKeys, Slack, Discord, and Telegram webhook URLs with embedded bot tokens, and Authorization header values. This occurs for authenticated admins or personal access tokens with nezha:ddns:read or nezha:notification:read scopes. The issue affects versions prior to 2.2.5 and is resolved in 2.2.5.
Potential Impact
Sensitive third-party API credentials and authorization tokens are exposed to any authenticated user with specific read permissions, potentially allowing unauthorized access to integrated services. This exposure could lead to misuse of these credentials if an attacker gains the required access scope. However, exploitation requires authenticated access with elevated privileges.
Mitigation Recommendations
A fix is available in Nezha Monitoring version 2.2.5. Users should upgrade to version 2.2.5 or later to remediate this vulnerability. Since this is a self-hosted product, administrators must apply the update to their installations. The vendor manages remediation for the cloud service version. No additional mitigation steps are indicated in the advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-02T16:50:27.886Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
- Is Cloud Service
- true
Threat ID: 6a516c2f68715ace434382a6
Added to database: 07/10/2026, 22:03:27 UTC
Last enriched: 07/18/2026, 15:31:14 UTC
Last updated: 08/24/2026, 22:52:12 UTC
Views: 78
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.