How severe is GHSA-c73q-8xxr-rgqm?

No CVSS score has been assigned to GHSA-c73q-8xxr-rgqm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-c73q-8xxr-rgqm?

GHSA-c73q-8xxr-rgqm affects the following packages: github.com/tilt-dev/tilt (Go). Ecosystems affected: Go.

How do I fix GHSA-c73q-8xxr-rgqm?

Update github.com/tilt-dev/tilt to 0.37.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c73q-8xxr-rgqm is resolved across your whole dependency graph.

How do I detect GHSA-c73q-8xxr-rgqm in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/tilt-dev/tilt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-c73q-8xxr-rgqm if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-c73q-8xxr-rgqm actively exploited in the wild?

No public exploit code has been indexed for GHSA-c73q-8xxr-rgqm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-c73q-8xxr-rgqm?

GHSA-c73q-8xxr-rgqm has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 41th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-c73q-8xxr-rgqm?

GHSA-c73q-8xxr-rgqm is classified as Missing Authentication (CWE-306). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-c73q-8xxr-rgqm published, and has it been updated?

GHSA-c73q-8xxr-rgqm was published on June 19, 2026 and was last updated on June 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

Tilt: Missing authentication on the network-exposed Tilt HUD serverGHSA-c73q-8xxr-rgqm

Fix: tilt-dev/tilt#6776

GHSA-c73q-8xxr-rgqm is a Missing Authentication vulnerability in github.com/tilt-dev/tilt. A fix is available for github.com/tilt-dev/tilt — see the affected versions and patch details below.

Also known asCVE-2026-55884GO-2026-5317

Published

Jun 19, 2026

Updated

Jun 25, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-c73q-8xxr-rgqm.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs41th percentile — riskier than 41% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/tilt-dev/tilt

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

The 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.

Details

The 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.

Impact

An 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.

Conditions for exploitation

Affected version in >= 0.20.8, <= 0.37.3.
HUD bound to a non-loopback address (tilt up --host 0.0.0.0, or TILT_HOST set).
Network reachability to the listener (default port 10350).

Not affected

The default loopback-only bind is not reachable from the network.

Workarounds

Use 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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/tilt-dev/tilt`	≥ 0.20.8&&< 0.37.4	0.37.4`go get github.com/tilt-dev/tilt@v0.37.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/tilt-dev/tilt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/tilt-dev/tilt to 0.37.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c73q-8xxr-rgqm is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

## Summary The 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. ## Details The 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 t

O3 Security · Impact-Aware SCA

Is GHSA-c73q-8xxr-rgqm in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works