# CVE-2026-111387: Nezha 2.2.5 before 2.3.15 Information Disclosure via DDNS List Endpoint

> Authenticated users can retrieve cleartext third-party credentials from DDNS webhook profiles due to missing data redaction in the API.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-7922-f42v-j7c8, GHSA-hpfr-cmgc-f455

## What is CVE-2026-111387?

CVE-2026-111387 is a high-severity vulnerability in nezhahq nezha, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Nezha from 2.2.5 before 2.3.15 contains an information disclosure vulnerability that allows authenticated users to retrieve third-party credentials because listDDNS omits WebhookURL and WebhookRequestBody redaction. Admins or PATs with nezha:ddns:read scope can call GET /api/v1/ddns to read cleartext tokens embedded in every user's DDNS webhook profiles.

Weakness: CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer)

## Which versions are affected by CVE-2026-111387?


## How do I fix CVE-2026-111387?

No fix has been published for CVE-2026-111387 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-111387 being exploited?

There is no known exploitation of CVE-2026-111387 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-111387 and fix it if it is affected.

What it is: CVE-2026-111387 is a high-severity vulnerability in nezhahq nezha, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-111387 in the wild and no public exploit code.

Affected product: nezhahq nezha. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-111387/ (Markdown: https://insights.sbomify.com/CVE-2026-111387/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-111387
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-111387
- OSV: https://osv.dev/vulnerability/CVE-2026-111387

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-111387/
Summaries are generated and may contain mistakes; the official description above is the record.