Diagnostics Prometheus
Monthly
An authenticated caller whose effective role deliberately lacks the operator.read scope can still retrieve the full Prometheus diagnostics document from the @openclaw/diagnostics-prometheus plugin in OpenClaw versions before 2026.9.3, because the plugin's authenticated metrics endpoint does not enforce the scope that ordinary read methods do. The result is limited information disclosure of operational metrics to a profile that was intentionally restricted below read access - confidentiality impact only, with no integrity or availability effect. Exploitation requires the Gateway to run in an identity-bearing authentication mode (for example trusted-proxy) and the attacker to already hold a valid authenticated profile, so shared-secret Gateway callers and default deployments that disable or restrict the endpoint are unaffected; no public exploit code was identified at time of analysis and the issue is fixed in 2026.9.3.
An authenticated caller whose effective role deliberately lacks the operator.read scope can still retrieve the full Prometheus diagnostics document from the @openclaw/diagnostics-prometheus plugin in OpenClaw versions before 2026.9.3, because the plugin's authenticated metrics endpoint does not enforce the scope that ordinary read methods do. The result is limited information disclosure of operational metrics to a profile that was intentionally restricted below read access - confidentiality impact only, with no integrity or availability effect. Exploitation requires the Gateway to run in an identity-bearing authentication mode (for example trusted-proxy) and the attacker to already hold a valid authenticated profile, so shared-secret Gateway callers and default deployments that disable or restrict the endpoint are unaffected; no public exploit code was identified at time of analysis and the issue is fixed in 2026.9.3.