CVE-2026-55884: Tilt: Missing authentication on the network-exposed Tilt HUD server
Tilt defines dev environments as code for microservice apps on Kubernetes. From 0.20.8 through 0.37.3, the Tilt HUD HTTP server registers handlers on a gorilla/mux router with no authenticating middleware. When the HUD is bound to a non-loopback address, an unauthenticated network caller 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. This issue is fixed in version 0.37.4.
Security readout for executives and security teams
Plain-English summary
CVE-2026-55884 is a critical authentication flaw in Tilt’s web HUD. If a developer runs affected Tilt versions with the HUD reachable beyond localhost, anyone who can reach it may control development resources and read sensitive runtime state, including a session token. The vendor-fixed version is 0.37.4.
Executive priority
Treat as urgent for teams using Tilt in network-accessible development environments. The business risk is developer-environment compromise and possible misuse of Kubernetes-facing capabilities. Prioritize upgrade and exposure review, especially on shared networks.
Technical view
Tilt versions 0.20.8 through 0.37.3 register HUD HTTP handlers without authentication middleware. With the HUD bound to a non-loopback address, unauthenticated network callers can trigger developer-defined resources, alter Tiltfile arguments, read engine state, and use the token-attaching /proxy handler to invoke apiserver resources. This maps to CWE-306 and CVSS 4.0 score 9.2.
Likely exposure
Exposure is most likely in developer workstations, shared dev servers, CI-like environments, or Kubernetes development hosts where Tilt HUD listens on a non-loopback interface. Localhost-only HUD use is materially less exposed based on the advisory description.
Exploitation context
Sources do not indicate active exploitation, and this CVE is not listed as KEV in the provided bundle. Exploitation requires network access to an affected, non-loopback-bound Tilt HUD. No user interaction or prior authentication is described.
Researcher notes
The key condition is HUD reachability beyond loopback. The advisory names missing authentication on gorilla/mux handlers and sensitive effects through resource actions, Tiltfile argument tampering, engine-state disclosure, and token-attaching proxy behavior. Avoid assuming internet-wide exposure without asset evidence.
Mitigation direction
Upgrade Tilt to version 0.37.4 or later.
Restrict Tilt HUD binding to localhost where possible.
Limit network access to developer HUD ports.
Review vendor advisory and release notes for environment-specific guidance.
Rotate exposed session tokens if HUD exposure is suspected.
Validation and detection
Inventory Tilt versions across developer and build environments.
Identify any Tilt HUD bound to non-loopback addresses.
Confirm upgraded hosts report Tilt 0.37.4 or later.
Review network controls limiting access to the HUD.
Check logs for unexpected HUD access if exposure existed.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
5Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-306 · source CWE mapping
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.