Finding / heypi

2026-10-13-heypi-older-admin-applications-already-enabled-authentication-by-default

Older admin applications already enabled authentication by default. The rewritten admin server gained required non-loopback bearer-token authentication on 2026-07-10, included in 0.3.0-beta.0. The older 0.1.3 and 0.2.0-beta.0 admin applications already had authentication enabled by default. Current admin construction is opt-in, defaults to 127.0.0.1 and refuses non-loopback startup without a token; wildcard bindings also require configured hosts. The secret-submission route is handled before the general bearer check and has its own request/host handling, so the token statement must not be generalized to every endpoint.

Channel: tagged-release legacy 0.1.3; preview-or-beta old beta.0 and current 0.3 beta; historical correction, no new advisory. Half: both. Date: 2026-06-04 (legacy 0.1.3); rewritten-server fix 2026-07-10; factual correction for the 2026-10-13 profile.

Operator consequence: Withdraw the earlier profile’s categorical pre-0.3 unauthenticated-admin allegation and blanket disclosure/rotation advice. Only an independently verified exposed revision or deployment could justify that advice. For current beta administration, retain loopback or explicitly configure token/hosts and review the secret handoff separately. This corrects a factual error; it is not an October fix or a new security advisory.

Receipt

Finding metadata

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

Finding ID: 2026-10-13-heypi-older-admin-applications-already-enabled-authentication-by-default

Profile citations

  • heypi / claim / legacy-admin-auth-correction
  • heypi / claim / admin-opt-in-loopback-and-token
  • heypi / posture / governance

Source links

Primary links, including exact changelog lines when available.