{"id":"CVE-2026-55884","title":"Tilt: Missing authentication on the network-exposed Tilt HUD server","summary":"Tilt: Missing authentication on the network-exposed Tilt HUD server","severity":"critical","cwe":["CWE-306"],"vendor":"tilt-dev","product":"github.com/tilt-dev/tilt","affected":["github.com/tilt-dev/tilt >= 0.20.8, <= 0.37.3"],"patched":["github.com/tilt-dev/tilt 0.37.4"],"published":"2026-06-19","updated":"2026-06-19","source":"GHSA","sourceUrl":"https://github.com/advisories/GHSA-c73q-8xxr-rgqm","references":[{"url":"https://github.com/tilt-dev/tilt/security/advisories/GHSA-c73q-8xxr-rgqm"},{"url":"https://github.com/tilt-dev/tilt/pull/6776"},{"url":"https://github.com/tilt-dev/tilt/releases/tag/v0.37.4"},{"url":"https://github.com/advisories/GHSA-c73q-8xxr-rgqm"}],"tags":["ghsa","go"],"ingestedAt":"2026-06-22T15:59:08.204Z","ecosystem":"go","epss":0.00496,"epssPercentile":0.39916,"slug":"CVE-2026-55884","body":"## Overview\n\n## Summary\nThe Tilt HUD HTTP server exposes state-changing and sensitive-read endpoints with no authentication. When the HUD is bound to a non-loopback address, a network attacker can trigger the developer's pre-defined Tiltfile resources, tamper with Tiltfile arguments, read full engine state including the session token, and reach the Tilt apiserver through a token-attaching proxy.\n\n## Details\nThe HUD server registers its handlers on a `gorilla/mux` router with no authenticating middleware. The `cookieWrapper` helper emits the `Tilt-Token` cookie but never validates it, and is attached only to the static-asset prefix.\n\n## Impact\nAn unauthenticated network caller can force any developer-defined resource to run on the host as the `tilt` user (choosing which and when, not the command text), set arbitrary Tiltfile arguments, disclose the session token and full engine state, and invoke apiserver resources via the loopback-token proxy. Because `tilt up` runs with the developer's privileges and credentials, the impact reaches the developer's environment and cluster.\n\n### Conditions for exploitation\n- Affected version in `>= 0.20.8, <= 0.37.3`.\n- HUD bound to a non-loopback address (`tilt up --host 0.0.0.0`, or `TILT_HOST` set).\n- Network reachability to the listener (default port `10350`).\n\n### Not affected\n- The default loopback-only bind is not reachable from the network.\n\n## Workarounds\nUse the default loopback bind (omit `--host`, unset `TILT_HOST`) and ensure nothing else proxies to `localhost:10350`. No complete workaround short of upgrading for non-loopback deployments.\n\n## Affected packages\n\n- `github.com/tilt-dev/tilt >= 0.20.8, <= 0.37.3`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `github.com/tilt-dev/tilt 0.37.4`","depth":"midnight","depthScore":52,"depthScoreParts":{"impact":52.3,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}