Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.268entry #51

Claude Code v2.1.268 ·

Gateway warns when it may be reachable from outside a trusted network

The self-hosted gateway now warns about unrestricted public access and logs how it determines client IPs

Group of 3 You'll notice Improvements
JSON All of v2.1.268
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
GatewayArea: what it touches
ImprovementsKind: in v2.1.268,
ImprovementsSection of the release

What

  • The gateway checks incoming client IPs against an expanded private-address list (now including 169.254.0.0/16 and fe80::/10 link-local ranges) and, if access_control.allow_cidrs is unset and a request arrives from a non-private address, emits a one-time warning that the gateway may be reachable from the public internet, since it can push settings that execute commands on developer machines.
  • Gateway config validation separately emits a warning when access_control.allow_cidrs is empty and the listener isn't otherwise locally-bound, warning that the gateway will accept any client address.
  • Server startup now logs whether client IPs are read from the raw TCP peer address or from the X-Forwarded-For header (based on the configured trusted proxies), including how many trusted-proxy entries are configured.

Why These changes help operators of a self-hosted gateway notice if it's exposed to the public internet or misconfigured around trusted proxies, which matters because the gateway can push settings that run commands on developer machines.

Read from
Names in the bundleaccess_control.allow_cidrs
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up access_control.allow_cidrs, on Claude apps gateway for Amazon Bedrock, Claude Platform on AWS, Google Cloud, and Microsoft Foundry. The gateway also logs a warning that `access_control.allow_cidrs` is empty. That's expected here, because nothing limits which client addresses the gateway serves until you set an allow list. The [`access_control` reference](/docs/en/claud… claude-apps-gateway see the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up access_control.allow_cidrs, on Claude apps gateway for Amazon Bedrock, Claude Platform on…
Anthropic's release notes agreeAdded a startup warning for gateways when access_control.allow_cidrs is empty, and a one-time warning the first time a request arrives from…

See this entry in the whole of v2.1.268 →

Feedback