fix(security): default standalone servers to loopback bind by davidrudduck · Pull Request #13184 · openclaw/openclaw

davidrudduck · 2026-02-10T06:00:30Z

Summary

Default standalone HTTP servers (canvas-host, webhook listener) to bind on 127.0.0.1 instead of 0.0.0.0.
Prevents unintended network exposure when running on machines with public interfaces.
Users who need external access can still override via configuration.

Supersedes #12370 (accidentally closed during fork maintenance).

Test plan

Verify canvas host binds to localhost by default
Verify telegram webhook listener binds to localhost by default
Verify explicit bind address config still works when overridden

Greptile Overview

Greptile Summary

This PR hardens the default networking posture of the standalone HTTP servers by changing the default bind address from 0.0.0.0 to 127.0.0.1 in:

src/canvas-host/server.ts (canvas host)
src/telegram/webhook.ts (Telegram webhook listener)

The change reduces accidental exposure on machines with public interfaces while still allowing explicit overrides via config (listenHost / host).

One functional issue remains in the Telegram webhook server: when port: 0 is used (ephemeral port), the code constructs the webhook publicUrl using the requested port before the server is actually listening, resulting in http://…:0/... being registered with Telegram.

Confidence Score: 3/5

This PR is not safe to merge until the Telegram webhook URL/port handling is fixed for ephemeral ports.
Binding to loopback by default is a straightforward security hardening, but startTelegramWebhook currently registers a webhook URL using port prior to listen(). With port: 0, this deterministically produces an invalid :0 webhook URL and will break webhook delivery in any environment using an ephemeral port (including the existing unit test setup).
src/telegram/webhook.ts

Context used:

Context from dashboard - CLAUDE.md (source)
Context from dashboard - AGENTS.md (source)

greptile-apps

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

greptile-apps · 2026-02-10T06:01:28Z

src/telegram/webhook.ts

  const path = opts.path ?? "/telegram-webhook";
  const healthPath = opts.healthPath ?? "/healthz";
  const port = opts.port ?? 8787;
-  const host = opts.host ?? "0.0.0.0";
+  const host = opts.host ?? "127.0.0.1";
  const runtime = opts.runtime ?? defaultRuntime;


Port 0 breaks webhook URL

startTelegramWebhook uses const port = opts.port ?? 8787; and then builds publicUrl from that port before calling server.listen(port, host, ...). When callers pass port: 0 (tests do this, and other callers may for ephemeral ports), the server binds to a random port but publicUrl becomes http://127.0.0.1:0/..., so bot.api.setWebhook(publicUrl, ...) registers an unusable URL. Compute the URL after listen() using server.address().port (or require a non-zero port when publicUrl isn’t explicitly provided).

Prompt To Fix With AI

This is a comment left during a code review. Path: src/telegram/webhook.ts Line: 33:37 Comment: **Port 0 breaks webhook URL** `startTelegramWebhook` uses `const port = opts.port ?? 8787;` and then builds `publicUrl` from that `port` before calling `server.listen(port, host, ...)`. When callers pass `port: 0` (tests do this, and other callers may for ephemeral ports), the server binds to a random port but `publicUrl` becomes `http://127.0.0.1:0/...`, so `bot.api.setWebhook(publicUrl, ...)` registers an unusable URL. Compute the URL after `listen()` using `server.address().port` (or require a non-zero port when `publicUrl` isn’t explicitly provided). How can I resolve this? If you propose a fix, please make it concise.

This is a pre-existing issue in the telegram webhook setup, not introduced by our change. Our PR only changes the default bind host from 0.0.0.0 to 127.0.0.1 — the port resolution logic is unchanged.

Change canvas host and telegram webhook default bind from 0.0.0.0 (all interfaces) to 127.0.0.1 (loopback only) to prevent unintended network exposure when no explicit host is configured.

@davidrudduck

…faults (openclaw#13184) thanks @davidrudduck

…idrudduck

…idrudduck

@davidrudduck

…13184) * fix(security): default standalone servers to loopback bind (openclaw#4) Change canvas host and telegram webhook default bind from 0.0.0.0 (all interfaces) to 127.0.0.1 (loopback only) to prevent unintended network exposure when no explicit host is configured. * fix: restore telegram webhook host override while keeping loopback defaults (openclaw#13184) thanks @davidrudduck * style: format telegram docs after rebase (openclaw#13184) thanks @davidrudduck --------- Co-authored-by: Peter Steinberger <steipete@gmail.com>

@davidrudduck

…13184) * fix(security): default standalone servers to loopback bind (openclaw#4) Change canvas host and telegram webhook default bind from 0.0.0.0 (all interfaces) to 127.0.0.1 (loopback only) to prevent unintended network exposure when no explicit host is configured. * fix: restore telegram webhook host override while keeping loopback defaults (openclaw#13184) thanks @davidrudduck * style: format telegram docs after rebase (openclaw#13184) thanks @davidrudduck --------- Co-authored-by: Peter Steinberger <steipete@gmail.com>

@davidrudduck

…13184) * fix(security): default standalone servers to loopback bind (openclaw#4) Change canvas host and telegram webhook default bind from 0.0.0.0 (all interfaces) to 127.0.0.1 (loopback only) to prevent unintended network exposure when no explicit host is configured. * fix: restore telegram webhook host override while keeping loopback defaults (openclaw#13184) thanks @davidrudduck * style: format telegram docs after rebase (openclaw#13184) thanks @davidrudduck --------- Co-authored-by: Peter Steinberger <steipete@gmail.com>

@davidrudduck

…13184) * fix(security): default standalone servers to loopback bind (openclaw#4) Change canvas host and telegram webhook default bind from 0.0.0.0 (all interfaces) to 127.0.0.1 (loopback only) to prevent unintended network exposure when no explicit host is configured. * fix: restore telegram webhook host override while keeping loopback defaults (openclaw#13184) thanks @davidrudduck * style: format telegram docs after rebase (openclaw#13184) thanks @davidrudduck --------- Co-authored-by: Peter Steinberger <steipete@gmail.com>

@davidrudduck

…13184) * fix(security): default standalone servers to loopback bind (openclaw#4) Change canvas host and telegram webhook default bind from 0.0.0.0 (all interfaces) to 127.0.0.1 (loopback only) to prevent unintended network exposure when no explicit host is configured. * fix: restore telegram webhook host override while keeping loopback defaults (openclaw#13184) thanks @davidrudduck * style: format telegram docs after rebase (openclaw#13184) thanks @davidrudduck --------- Co-authored-by: Peter Steinberger <steipete@gmail.com>

@davidrudduck

…13184) * fix(security): default standalone servers to loopback bind (#4) Change canvas host and telegram webhook default bind from 0.0.0.0 (all interfaces) to 127.0.0.1 (loopback only) to prevent unintended network exposure when no explicit host is configured. * fix: restore telegram webhook host override while keeping loopback defaults (openclaw#13184) thanks @davidrudduck * style: format telegram docs after rebase (openclaw#13184) thanks @davidrudduck --------- Co-authored-by: Peter Steinberger <steipete@gmail.com> (cherry picked from commit 5643a93) # Conflicts: # CHANGELOG.md # docs/channels/telegram.md

@davidrudduck

…13184) * fix(security): default standalone servers to loopback bind (#4) Change canvas host and telegram webhook default bind from 0.0.0.0 (all interfaces) to 127.0.0.1 (loopback only) to prevent unintended network exposure when no explicit host is configured. * fix: restore telegram webhook host override while keeping loopback defaults (openclaw#13184) thanks @davidrudduck * style: format telegram docs after rebase (openclaw#13184) thanks @davidrudduck --------- Co-authored-by: Peter Steinberger <steipete@gmail.com> (cherry picked from commit 5643a93) # Conflicts: # CHANGELOG.md # docs/channels/telegram.md # src/telegram/monitor.ts

@davidrudduck

…13184) * fix(security): default standalone servers to loopback bind (#4) Change canvas host and telegram webhook default bind from 0.0.0.0 (all interfaces) to 127.0.0.1 (loopback only) to prevent unintended network exposure when no explicit host is configured. * fix: restore telegram webhook host override while keeping loopback defaults (openclaw#13184) thanks @davidrudduck * style: format telegram docs after rebase (openclaw#13184) thanks @davidrudduck --------- Co-authored-by: Peter Steinberger <steipete@gmail.com>

openclaw-barnacle bot added the channel: telegram Channel integration: telegram label Feb 10, 2026

greptile-apps bot reviewed Feb 10, 2026

View reviewed changes

sebslight mentioned this pull request Feb 13, 2026

fix(canvas-host): bind to loopback by default #2423

Closed

steipete self-assigned this Feb 13, 2026

davidrudduck and others added 3 commits February 13, 2026 16:36

fix(security): default standalone servers to loopback bind (#4)

d334f53

Change canvas host and telegram webhook default bind from 0.0.0.0 (all interfaces) to 127.0.0.1 (loopback only) to prevent unintended network exposure when no explicit host is configured.

fix: restore telegram webhook host override while keeping loopback de…

7c26447

…faults (openclaw#13184) thanks @davidrudduck

style: format telegram docs after rebase (openclaw#13184) thanks @dav…

ce4ee67

…idrudduck

steipete force-pushed the fix/default-bind-loopback branch from 986ffed to ce4ee67 Compare February 13, 2026 15:37

steipete merged commit 5643a93 into openclaw:main Feb 13, 2026
9 checks passed

openclaw-barnacle bot added docs Improvements or additions to documentation size: XS labels Feb 13, 2026

github-actions bot mentioned this pull request Feb 13, 2026

📡 Upstream Digest — 2026-02-13 16:36 UTC curtismercier/openclaw-mods#15

Open

This was referenced Feb 14, 2026

[OpenClaw #13184] Bind standalone server defaults to loopback for safer local exposure adolago/zee#332

Closed

Fix #332: default standalone server bind to loopback adolago/zee#380

Merged

dinakars777 mentioned this pull request Feb 14, 2026

Harden Debug UI defaults: loopback-only binding + warnings #6590

Closed

davidrudduck deleted the fix/default-bind-loopback branch February 14, 2026 11:04

nickytonline mentioned this pull request Feb 14, 2026

nickytonline/trusted auth docs update nickytonline/openclaw#1

Closed

This was referenced Mar 1, 2026

cherry-pick: upstream deps/security commits (2026-03-01-0443) hughdidit/DAISy-Agency#138

Closed

cherry-pick: upstream deps/security commits (2026-03-02-2346) hughdidit/DAISy-Agency#144

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(security): default standalone servers to loopback bind#13184

fix(security): default standalone servers to loopback bind#13184
steipete merged 3 commits intoopenclaw:mainfrom
davidrudduck:fix/default-bind-loopback

davidrudduck commented Feb 10, 2026 •

edited by greptile-apps bot

Loading

Uh oh!

greptile-apps bot left a comment

Uh oh!

greptile-apps bot Feb 10, 2026

Uh oh!

davidrudduck Feb 12, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

davidrudduck commented Feb 10, 2026 • edited by greptile-apps bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Test plan

Greptile Overview

Greptile Summary

Confidence Score: 3/5

Uh oh!

greptile-apps bot left a comment

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Feb 10, 2026

Choose a reason for hiding this comment

Uh oh!

davidrudduck Feb 12, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

davidrudduck commented Feb 10, 2026 •

edited by greptile-apps bot

Loading