CVE Intelligence
Medium

CVE-2026-111386 — Nezha 1.7.0 before 2.3.15 Cross-Tenant Server-ID Enumeration via getServerConfig

Nezha from 1.7.0 before 2.3.15 contains an information disclosure vulnerability that allows authenticated members to enumerate other tenants' server IDs through differential responses. Attackers can sweep sequential IDs against getServerConfig and setServerConfig, distinguishing 'permission denied' from success payloads to map other users' servers.

Published Oct 16, 2026 · Updated Oct 16, 2026 · Sources: CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database · CNA: VulnCheck

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • Technical severity (medium)+3
  • CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
Nezhahq
Nezha
CVSS base
4.3
Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Proof of concept
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Nezhahq Nezha).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Nezhahq Nezha ≥ 1.7.0 and < 2.3.15 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.3 CVSS 4.0 Medium — — disclosure@vulncheck.com via NIST National Vulnerability Database
5.3 CVSS 4.0 Medium — — VulnCheck via CVE Program (cve.org) e CISA ADP
4.3 CVSS 3.1 Medium 2.8 1.4 disclosure@vulncheck.com via NIST National Vulnerability Database
4.3 CVSS 3.1 Medium — — VulnCheck via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-204

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 16, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · Published → Deferred
    Oct 16, 2026 · NIST National Vulnerability Database
  • CVE published
    Oct 16, 2026 · VulnCheck
  • Record published
    Oct 16, 2026
  • CVSS changed · 4.3
    Oct 16, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 16, 2026 · CVE Program (cve.org) e CISA ADP
  • Record created in this database
    Oct 16, 2026 · CVE Program (cve.org) e CISA ADP

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 16, 2026 – Oct 16, 2026

References

3 on the record

Elsewhere on this site

Nezhahq
every CVE for this vendor
CWE-204
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2026-111387 Nezha 2.2.5 before 2.3.15 Information Disclosure via DDNS List Endpoint 11h
  • Medium CVE-2026-111383 Nezha 2.0.13 before 2.3.15 Denial of Service via /api/v1/ws/transfer WebSocket 11h
  • Medium CVE-2026-111385 Nezha 2.1.0 before 2.3.15 Host Header Injection via MCP Transfer Tools 11h
  • Medium CVE-2026-111384 Nezha 1.0.0 before 2.3.15 Memory Exhaustion via File Manager WebSocket 11h
  • Medium CVE-2026-100394 Nezha Monitoring: Whole-instance DoS in Nezha dashboard: a member can crash the process for every tenant 1d
  • Medium CVE-2026-105112 Nezha 1.8.0 before 2.3.13 Deadlock DoS via notification-group endpoints 13d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No FIRST EPSS score.
  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-111386 is "Nezha 1.7.0 before 2.3.15 Cross-Tenant Server-ID Enumeration via getServerConfig", rated Medium. It affects Nezha (Nezhahq); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.3 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.