Quick answers
- Is CVE-2026-111386 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111386 being exploited in the wild.
- How severe is CVE-2026-111386?
- Medium severity, with a CVSS score of 4.3, published 16 October 2026.
- Which products and versions are affected?
- Nezha 1.7.0 before 2.3.15.
- Is there a fix for CVE-2026-111386?
- Yes: fixed in 2.3.15. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111386 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-111386?
- Check whether you run Nezha at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.3.15
Technical details
The vulnerability exists in the getServerConfig and setServerConfig API endpoints which return distinguishable responses for non-existent server IDs versus existing servers owned by other users. An authenticated member (RoleMember) can sweep sequential server IDs, observing "permission denied" errors for existing foreign servers and success payloads for absent IDs, allowing enumeration of all servers in the multi-tenant deployment. The root cause is inconsistent authorization response handling compared to the forceUpdateServer endpoint which properly hides both cases.
Affected products
- Nezha Nezha 1.7.0 before 2.3.15
Timeline
- 2026-10-01: disclosed
- 2026-10-16: advisory