CVE-2026-111386 nezhahq CVE debrief

Who should care

Defenders and administrators of Nezha instances, especially in multi-tenant environments, should assess the exposure and potential impact of this vulnerability. They should verify Nezha instance versions and exposure in multi-tenant environments, assess the impact of this vulnerability on systems, and monitor for potential exploitation attempts.

Why it matters

CVE-2026-111386 is a medium-severity information disclosure vulnerability in Nezha versions 1.7.0 before 2.3.15. Authenticated members can enumerate other tenants' server IDs through differential responses when sweeping sequential IDs against getServerConfig and setServerConfig.

• Verification of Nezha instance versions and exposure in multi-tenant environments is necessary
• Potential enumeration of other tenants' server IDs through differential responses
• Monitoring for potential exploitation attempts is recommended

Technical summary

The vulnerability allows authenticated members to enumerate other tenants' server IDs through differential responses when sweeping sequential IDs against getServerConfig and setServerConfig. This requires defenders to verify exposure of Nezha instances, especially in multi-tenant environments, and assess the impact of this vulnerability on their systems. Affected product deployments should be verified in managed environments, and owners should be assigned for follow-up. The vulnerability allows authenticated members to enumerate other tenants' server IDs through differential responses when sweeping sequential IDs against getServerConfig and setServerConfig.

Defensive priority

Defenders should prioritize verifying exposure of Nezha instances, especially in multi-tenant environments, and assess the impact of this vulnerability on their systems.

Recommended defensive actions

• Verify Nezha instance versions and exposure in multi-tenant environments
• Assess the impact of this vulnerability on systems
• Monitor for potential exploitation attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. However, the exact scope of affected versions and potential impact require further verification from official sources. Affected product deployments should be verified in managed environments, and owners should be assigned for follow-up. The vulnerability allows authenticated members to enumerate other tenants' server IDs through differential responses when sweeping sequential IDs against getServerConfig and setServerConfig. This requires defenders to verify exposure,

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.