CVE-2026-55884: Tilt HUD Auth Bypass Vulnerability

CVE-2026-55884 Overview

CVE-2026-55884 is a missing authentication vulnerability [CWE-306] in Tilt, a tool that defines development environments as code for microservice applications on Kubernetes. The Tilt HUD HTTP server registers handlers on a gorilla/mux router without any authenticating middleware. When the HUD binds to a non-loopback address, an unauthenticated network attacker can trigger developer-defined resources, tamper with Tiltfile arguments, read full engine state including the session token, and invoke apiserver resources through the token-attaching /proxy handler. The flaw affects versions 0.20.8 through 0.37.3 and is fixed in 0.37.4.

Critical Impact
Unauthenticated network attackers can execute developer-defined actions, exfiltrate session tokens, and proxy authenticated requests to the Kubernetes apiserver.

Affected Products

Tilt versions 0.20.8 through 0.37.3
Tilt HUD HTTP server component bound to non-loopback addresses
Development environments exposing Tilt via TILT_HOST or --host set to 0.0.0.0

Discovery Timeline

2026-07-10 - CVE-2026-55884 published to NVD
2026-07-15 - Last updated in NVD database

Technical Details for CVE-2026-55884

Vulnerability Analysis

The Tilt HUD server exposes a control plane intended for local developer interaction. HTTP handlers are registered on a gorilla/mux router, but no authenticating middleware wraps the mutating or sensitive routes. When Tilt is launched with --host 0.0.0.0 or an equivalent non-loopback bind, these endpoints become reachable from any network peer that can route to the developer's machine.

An attacker reaching the HUD can invoke developer-defined resources, mutate Tiltfile arguments to alter build and deploy behavior, and read engine state that includes the session token. That token is auto-attached by the /proxy handler when it forwards requests to the Kubernetes apiserver, so the attacker inherits the developer's cluster privileges. This yields code execution paths through resource triggers and full apiserver access constrained only by the developer's kubeconfig.

Root Cause

The root cause is missing authentication on privileged HTTP handlers. The default --host value was localhost, but the flag documentation invited users to set 0.0.0.0 without warning about the consequences. Because the router had no auth middleware, any request that reached the socket was honored.

Attack Vector

Exploitation requires network reachability to the HUD port and knowledge that a non-loopback bind is active. The attacker sends unauthenticated HTTP requests to trigger resources, patch Tiltfile arguments, retrieve state containing the session token, or issue apiserver calls via /proxy.

// Patch excerpt: internal/cli/flags.go — updated flag help warns about remote exposure
// For commands that start a web server.
func addStartServerFlags(cmd *cobra.Command) {
	cmd.Flags().IntVar(&webPortFlag, "port", defaultWebPort,
		"Port for the Tilt HTTP server. Set to 0 to disable. Overrides TILT_PORT env variable.")
	cmd.Flags().StringVar(&webHostFlag, "host", defaultWebHost,
		"Host for the Tilt HTTP server and default host for any port-forwards. "+
			"Defaults to localhost; only change this if you need remote access "+
			"and understand the security implications. Overrides TILT_HOST env variable.")
}

Source: GitHub Commit 47393fb. The patch also wires the HUD server to enforce token checks via imports from internal/hud/server and internal/token in internal/cli/utils.go.

Detection Methods for CVE-2026-55884

Indicators of Compromise

Tilt processes launched with --host 0.0.0.0, --host <public-IP>, or TILT_HOST set to a non-loopback value.
Inbound HTTP requests to the Tilt HUD port from addresses outside the developer workstation loopback interface.
Unexpected invocations of /proxy, resource trigger endpoints, or Tiltfile argument mutations in HUD access logs.
Kubernetes audit log entries showing apiserver calls originating from a developer session token at unusual times or from unusual user agents.

Detection Strategies

Inventory running Tilt versions across developer endpoints and flag any instance in the range 0.20.8 to 0.37.3.
Monitor process command lines and environment for TILT_HOST values that are not 127.0.0.1 or localhost.
Correlate HUD server access logs with Kubernetes audit logs to identify proxied requests that did not originate from an interactive developer session.

Monitoring Recommendations

Alert on new listening sockets bound to 0.0.0.0 on developer machines, especially on the default Tilt port.
Track outbound connections from CI runners or shared dev hosts to the Tilt HUD port from unexpected sources.
Review Kubernetes RBAC scopes assigned to developer kubeconfigs used by Tilt and reduce privileges where possible.

How to Mitigate CVE-2026-55884

Immediate Actions Required

Upgrade Tilt to version 0.37.4 or later on all developer workstations and shared build hosts.
Reset any Kubernetes credentials that were loaded by a vulnerable Tilt instance bound to a non-loopback address.
Audit HUD access logs and Kubernetes audit logs for evidence of unauthenticated access during the exposure window.

Patch Information

The fix ships in Tilt release v0.37.4 via pull request #6776 and commit 47393fb. The patch secures mutating and sensitive HUD requests with token-based authentication and updates the --host flag guidance. Full advisory: GHSA-c73q-8xxr-rgqm.

Workarounds

Keep Tilt bound to localhost by omitting --host and unsetting TILT_HOST, or explicitly set --host 127.0.0.1.
If remote access is required, tunnel the HUD through SSH port-forwarding or a mutually authenticated reverse proxy rather than binding to 0.0.0.0.
Restrict developer workstation firewalls to block inbound traffic to the Tilt HUD port from any non-local source.

bash

# Configuration example: restrict Tilt HUD to loopback and verify version
unset TILT_HOST
tilt up --host 127.0.0.1 --port 10350

# Confirm patched version
tilt version   # expect v0.37.4 or later

# Optional: block remote access to the HUD port on Linux developer hosts
sudo iptables -A INPUT -p tcp --dport 10350 ! -s 127.0.0.1 -j DROP