OpenClaw 2026.11.1 blocks risky redirects and rejects FIFO-based hook credentials
The changelog lists fixes that stop ClickClack and ClawHub from following redirects into unrelated private services and remove browser private-network access from Discord CDN downloads.
OpenClaw 2026.11.1 changes how two of its outbound network clients handle redirects. ClickClack and ClawHub previously followed redirects wherever the server pointed them. The release now routes both through the project's existing SSRF guard, which blocks requests to private, loopback and metadata addresses outside the configured origin. The changelog states that ClickClack and ClawHub now reject redirects into unrelated private services, and that Discord CDN downloads no longer inherit browser private-network access. The same release also rejects FIFO native-hook credentials without hanging the agent. The notes credit several contributors for these fixes.
The ClickClack change came from a pull request by pgondhi987, merged on November 3, 2026. According to the PR description, the ClickClack API client used ambient fetch, so a configured server could redirect gateway requests to another private, loopback or metadata destination. The fix sends requests through the guarded fetch with exact configured-origin trust. Self-hosted private origins keep working and same-origin redirects are followed, but a redirect to any other origin is checked against the default policy. The PR also says that retired callers cannot make later HTTP writes, including redirected ones. The author's test output reports that a redirect to another private origin was rejected and that the protected server received no requests.
The ClawHub change is pull request #190939. The PR says ClawHub archive downloads could follow resolver URLs and redirects to private network services outside the configured registry origin. Downloads now reject private, loopback, link-local and metadata targets unless they sit at the operator-configured registry origin. The author reports a real local HTTP test in which a redirect and a direct resolver URL pointing to another private origin were both rejected with SsrFBlockedError, while the configured registry origin still downloaded successfully. The GitHub codeload origin gets the same explicit trust.
The compatibility cost is stated plainly in both PRs. An operator whose registry sends archives to a different private host will see those downloads fail, and the authors say such operators must serve the archives from the configured origin instead. The ClickClack PR says the same for cross-origin private redirects and points operators to the final API origin. A ClawSweeper review attached to each PR rated the change as a security repair with cleared security findings, but it labeled both changes as merge-risk for this compatibility reason.
The continuous integration results are less clean. The ClickClack PR snapshot reports 43 passed, 57 skipped and 3 failed statuses. The author attributes the failing boundary job to an existing Baseten test import that is unchanged from the base. The ClawHub PR reports 111 checks with one failure, the same boundary job, and a plugin-search timeout that the author says also reproduces on the base. The ClawHub PR was merged on November 3, 2026, and both PR pages attribute the boundary failure to code unchanged from the base.
The release notes also cover a separate Discord item. Discord CDN downloads no longer inherit browser private-network access. The changelog lists this with the ClickClack and ClawHub fixes under one network-and-tool-safety heading, and attributes all four of those pull requests to pgondhi987, SebTardif and Leon-SK668.
What changed
ClickClack and ClawHub outbound requests now go through the SSRF guard and reject redirects into private, loopback, link-local and metadata destinations outside the configured origin, and Discord CDN downloads no longer inherit browser private-network access.
Type: Security · Applies to: OpenClaw 2026.11.1, ClickClack, ClawHub, Discord CDN downloads
Why it matters
Operators running agent gateways that fetch remote resources could have exposed requests reaching internal services, so the patch matters beyond routine maintenance.
What you can do
Upgrade OpenClaw deployments to 2026.11.1 wherever ClickClack, ClawHub or Discord integrations are in use.
Original source
- github.comRelease openclaw 2026.11.1 · openclaw/openclaw · GitHub
- github.comfix(clickclack): block redirects to unrelated private services by pgondhi987 · Pull Request #190944 · openclaw/openclaw · GitHub
- github.comfix(clawhub): block archive redirects to private network targets by pgondhi987 · Pull Request #190939 · openclaw/openclaw · GitHub
Where we saw it
OpenClaw releases
AI wrote this summary from the sources listed, and nobody reviewed it individually before publication. Check the original source before you rely on it. How it works