Bitter Frontier What coding agents just made possible, where the bottleneck moved, and what deserves attention.

Finding / openhands

2026-10-13-openhands-v1-25-0-stops-serving-the-session-key-to-the-network-npm-desktop-and-docker-installs-befor

v1.25.0 stops serving the session key to the network; npm, desktop and Docker installs before it exposed the key to anyone who could reach port 8000. Through v1.24.0 the npm agent-canvas launcher and the desktop app started the port-8000 ingress on every interface and the static server on ::, with the stack’s session API key written into the served HTML; the Docker image did the same, and its README quickstart published -p 8000:8000. Anyone who could reach the port could read the key and use it on the proxied agent-server and automation APIs. The report (#16879) was public with reproduction steps from 2026-08-24 and reproduced on v1.16.0. The fixed release shipped 43 days later. v1.25.0 binds npm and desktop listeners to 127.0.0.1 by default, refuses to inject the key when a listener is off loopback (the UI falls back to the API-key prompt used by --public), keeps the Docker image key-free unless AGENT_CANVAS_ALLOW_LAN_SESSION_KEY=true, and rewrites the Docker quickstart to publish on 127.0.0.1 with that opt-in. With OH_CONVERSATION_RUNTIME=docker the launcher deliberately binds the key-free stack to 0.0.0.0 so conversation containers can reach it through host.docker.internal. No advisory was filed, and the docs site’s v1.25.0 release notes mention neither the fix nor the Docker behavior change.

Channel: tagged-release. Half: both. Date: 2026-10-06.

Operator consequence: Run v1.25.0 or later (v1.27.1). If you ran v1.24.0 or earlier through npm, the desktop app, or Docker published beyond loopback on a network others could reach, treat the session key as exposed: plan session-key rotation together with encrypted automation-state migration (the automation KV secret is derived from the key unless AUTOMATION_KV_SECRET is set), then review saved secrets, automations and recent conversations for activity you did not start. On Docker, do not rotate by setting LOCAL_BACKEND_API_KEY alone (section 2). After upgrading, an API-key prompt on a Docker quickstart without the new flags is the fix working. In per-conversation Docker mode, firewall port 8000, because the stack listens on every interface behind the key. Human attention: with no advisories, the ordinary PR and release diff, rather than an advisory alert, carry this warning.

Receipt

Finding metadata

Confidence
high

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-openhands-v1-25-0-stops-serving-the-session-key-to-the-network-npm-desktop-and-docker-installs-befor

Profile citations

Source links

Primary links, including exact changelog lines when available.

  1. OpenHands
    github release2026-10-13-openhands-v1-25-0-stops-serving-the-session-key-to-the-network-npm-desktop-and-docker-installs-beforOpenHands/OpenHands / v1.25.0merged pr2026-10-13-openhands-v1-25-0-stops-serving-the-session-key-to-the-network-npm-desktop-and-docker-installs-beforgithub.com/OpenHands/OpenHands/pull/17007official docs2026-10-13-openhands-v1-25-0-stops-serving-the-session-key-to-the-network-npm-desktop-and-docker-installs-beforgithub.com/OpenHands/OpenHands/issues/16879tagged commit file2026-10-13-openhands-v1-25-0-stops-serving-the-session-key-to-the-network-npm-desktop-and-docker-installs-beforOpenHands/OpenHands / scripts/bind-host.mjs#L8-L77tagged commit file2026-10-13-openhands-v1-25-0-stops-serving-the-session-key-to-the-network-npm-desktop-and-docker-installs-beforOpenHands/OpenHands / docker/entrypoint.sh#L395-L398tagged commit file2026-10-13-openhands-v1-25-0-stops-serving-the-session-key-to-the-network-npm-desktop-and-docker-installs-beforOpenHands/OpenHands / README.md#L142-L144tagged commit file2026-10-13-openhands-v1-25-0-stops-serving-the-session-key-to-the-network-npm-desktop-and-docker-installs-beforOpenHands/docs / openhands/usage/agent-canvas/release-notes/v1.25.0.mdx