CVE-2026-100525 openclaw CVE debrief

Who should care

Defenders and administrators of OpenClaw Prometheus diagnostics plugin deployments, especially those using identity-bearing Gateway authentication modes, should assess exposure and prioritize verification of the Prometheus endpoint's authentication scope enforcement.

Why it matters

The OpenClaw Prometheus diagnostics plugin issue allows authenticated callers with limited access to retrieve operational metrics, potentially disclosing sensitive information. Defenders should assess exposure, prioritize verification, and implement remediation measures.

• Authenticated profiles with limited access may be exposed to operational metrics.
• The issue may allow unintended disclosure of sensitive information.
• Verification of the Prometheus endpoint's authentication scope enforcement is necessary.
• Remediation or mitigation measures should be implemented to prevent exploitation.

Technical summary

The OpenClaw Prometheus diagnostics plugin before version 2026.9.3 does not enforce the operator.read scope on its authenticated metrics endpoint. This issue allows a caller with an effective role that has no read scope to retrieve the diagnostics document, disclosing operational metrics to an authenticated profile intentionally limited below read access. The issue is fixed in version 2026.9.3. As a workaround, disable the Prometheus endpoint or ensure every identity that can reach it is intended to hold operator.read. The CVE Program and NVD provide official records and vulnerability assessments.

Defensive priority

Defenders should assess exposure and prioritize verification of the Prometheus endpoint's authentication scope enforcement, especially in deployments using an identity-bearing Gateway authentication mode.

Recommended defensive actions

• Verify the Prometheus endpoint's authentication scope enforcement in your deployment.
• Assess the impact of the issue on your operational metrics and consider disabling the endpoint if not required.
• Update to version 2026.9.3 or later if possible.
• Review and adjust the identity and access management for the Prometheus endpoint.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Evidence notes

The issue is fixed in version 2026.9.3. As a workaround, disable the Prometheus endpoint or ensure every identity that can reach it is intended to hold operator.read. The CVE Program and NVD provide official records and vulnerability assessments.

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.