CVE-2026-59155

MEDIUMPre-NVD 6.96.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
6.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
6.9
EG Score
6.9(medium)
EPSS
22.3%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 13, 2026

Advisory Details (3)

Auto-updated Jul 10, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

DDNS and Notification credential exposure via unredacted list API · Advisory · nezhahq/nezha · GitHub

https://github.com/nezhahq/nezha/security/advisories/GHSA-ww5p-j6cj-6mqq
github_release Patch Available

v2.2.5

Patch available: nezhahq/nezha v2.2.5

https://github.com/nezhahq/nezha/releases/tag/v2.2.5
github_commit Patch Available

commit 39d398066d8c (nezhahq/nezha)

Patch available: nezhahq/nezha v2.2.5 (contains commit 39d398066d8c)

https://github.com/nezhahq/nezha/commit/39d398066d8c644fe452f74704e34ada6c7ab61e

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/nezhahq/nezha—2.2.5—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 15× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 11:22 UTCEG score recompute
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-14 13:27 UTCEG score recompute
  7. 2026-07-13 22:31 UTCEPSS rescore
  8. 2026-07-13 15:34 UTCEG score recompute
  9. 2026-07-13 06:13 UTCEPSS rescore
  10. 2026-07-13 06:13 UTCEPSS rescore
  11. 2026-07-12 17:40 UTCEG score recompute
  12. 2026-07-12 05:46 UTCEPSS rescore
  13. 2026-07-11 19:46 UTCEG score recompute
  14. 2026-07-10 21:52 UTCEG score recompute
  15. 2026-07-10 21:52 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-59155?
CVE-2026-59155 is a medium vulnerability published on July 10, 2026. 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…
When was CVE-2026-59155 disclosed?
CVE-2026-59155 was first published in the National Vulnerability Database on July 10, 2026, with the most recent update on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59155 actively exploited?
CVE-2026-59155 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-59155?
CVE-2026-59155 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-59155?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59155, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-59155

Explore →

Is Your Infrastructure Affected by CVE-2026-59155?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs