Gateway Control UI bootstrap config required Gateway auth.
When Gateway authentication was enabled, the Control UI bootstrap config endpoint could still be read without a valid Gateway token. That response could expose sensitive bootstrap/config fields intended only for authenticated Control UI sessions.
The bootstrap config route now goes through the same Gateway read-auth path as other authenticated Control UI reads. Regression tests cover unauthenticated rejection, valid-token access, and basePath handling.
OpenClaw thanks @zsxsoft for reporting.
{
"github_reviewed": true,
"severity": "MODERATE",
"nvd_published_at": null,
"cwe_ids": [
"CWE-287"
],
"github_reviewed_at": "2026-05-04T21:14:17Z"
}