# Tilt: Missing authentication on the network-exposed Tilt HUD server

Advisory record · `GHSA-c73q-8xxr-rgqm`

- **Identifiers:** `GHSA-c73q-8xxr-rgqm` · `CVE-2026-55884` · `GO-2026-5317`
- **State:** Confirmed
- **Severity:** CVSS 9.2 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-306](https://cwe.mitre.org/data/definitions/306.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 19 Jun 2026
- **Updated:** 25 Jun 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 19 Jun 2026, 13:58 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.2: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `github.com/tilt-dev/tilt` (Go): affected `>=0.20.8, <0.37.4`; fixed in `0.37.4`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Tilt (github.com/tilt-dev/tilt) versions 0.20.8 through 0.37.3 are affected when the HUD server is bound to a non-loopback address. A network attacker can reach the unauthenticated HUD endpoints to trigger pre-defined Tiltfile resources, set Tiltfile arguments, read engine state including the session token, and access the Tilt apiserver. Upgrade to 0.37.4. Keeping the default loopback bind (no --host flag and TILT_HOST unset) avoids exposure, but this is not a complete workaround for non-loopback deployments.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.2 Critical, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0050, the 43rd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:07 UTC: First seen by agentprime
- 31 Oct 2026, 15:07 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-c73q-8xxr-rgqm)

## Sources

- [GitHub Advisory Database: GHSA-c73q-8xxr-rgqm](https://github.com/advisories/GHSA-c73q-8xxr-rgqm)
- [OSV: GHSA-c73q-8xxr-rgqm](https://osv.dev/vulnerability/GHSA-c73q-8xxr-rgqm)
- <https://github.com/tilt-dev/tilt/security/advisories/GHSA-c73q-8xxr-rgqm>
- <https://github.com/tilt-dev/tilt/pull/6776>
- <https://github.com/tilt-dev/tilt>
- <https://github.com/tilt-dev/tilt/releases/tag/v0.37.4>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-c73q-8xxr-rgqm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-c73q-8xxr-rgqm/>. Everything for agents: <https://agentprime.io/llms.txt>.
