Executive brief
Tilt, a tool used by developers to manage microservice environments on Kubernetes, contains a security vulnerability in its dashboard (HUD) server. When the dashboard is configured to be accessible over a network rather than just the local machine, it fails to verify the identity of users. This allows an unauthorized person on the same network to view sensitive configuration files, modify development settings, and potentially gain control over the connected Kubernetes resources.
Technical details
The Tilt HUD HTTP server, which utilizes a gorilla/mux router, was found to register several sensitive handlers without authenticating middleware. When the server is bound to a non-loopback address (e.g., via the --host 0.0.0.0 flag), an unauthenticated remote attacker can access endpoints such as /api/view, /api/trigger, and /proxy/*. This allows for the extraction of the full engine state (including session tokens), tampering with Tiltfile arguments, and the invocation of Kubernetes apiserver resources through the token-attaching proxy handler. The vulnerability also included a WebSocket origin check bypass where omitting the Origin header allowed unauthorized access to the full view stream. The issue is resolved in version 0.37.4 by implementing CSRF protection, SameSite=Strict cookies, and mandatory token authentication for sensitive endpoints.
Affected products
- tilt-dev Tilt 0.20.8 through 0.37.3
Timeline
- 2026-06-15: patched: Fixes merged into master branch
- 2026-06-16: advisory: Release v0.37.4 published
- 2026-07-10: disclosed: CVE published to NVD