Advisory record · GHSA-ww5p-j6cj-6mqq

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

CVSS 6.9 MediumEPSS 0.0039 · 33rd percentile

Published by the GitHub Advisory Database at 26 Jun 2026, 23:55 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/nezhahq/nezhaGo<2.2.52.2.5
Identifiers
GHSA-ww5p-j6cj-6mqq · CVE-2026-59155 · GO-2026-5832
Weakness (CWE)
CWE-200
Published
26 Jun 2026
Updated
12 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Nezha Dashboard versions before 2.2.5 are affected. The DDNS and notification list endpoints return stored third-party credentials, including Cloudflare API tokens, TencentCloud SecretKeys, and webhook URLs or headers that may contain bot tokens, without redaction. An attacker who holds an admin session or a personal access token with the DDNS or notification read scope can read these secrets and use them to modify DNS records or send messages through the configured integrations. Upgrade to version 2.2.5 or later.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.9 Medium 4.0 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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0039, the 33rd percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:05 UTC First seen by agentprime
  2. 31 Oct 2026, 15:05 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.