dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-55884

CRITICAL · 9.2 CVSS v4.0 Published 2026-07-10
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Tilt HUD HTTP server binds to gorilla/mux router without authentication middleware. When bound to non-loopback addresses, unauthenticated remote attackers can trigger developer-defined resources, modify Tiltfile arguments, extract engine state including session tokens, and abuse the /proxy handler to invoke apiserver resources with attached tokens.

MitigationUpgrade Tilt to version 0.37.4 or later; alternatively, ensure the HUD is bound exclusively to loopback addresses (127.0.0.1/localhost) to prevent network exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Tilt HUD server is running
    Check running processes for Tilt and identify the port the HUD is serving on (default typically 10351)
    Affected if Tilt process is running with HUD enabled
  2. Determine the bind address of the Tilt HUD
    Inspect Tilt configuration or runtime environment for HUD bind address settings; check process environment variables or startup flags for HUD host binding
    Affected if The HUD is configured to bind to 0.0.0.0 or any non-loopback IP address rather than 127.0.0.1/localhost
  3. Verify network exposure of the HUD port
    Use netstat, ss, or similar tools to list listening ports and their bound addresses for the Tilt process
    Affected if The HUD port is listening on 0.0.0.0 or an external interface IP rather than 127.0.0.1
  4. Check for authentication middleware on the HTTP router
    Review Tilt source code or configuration for gorilla/mux router setup; verify if authentication middleware is applied before request handling
    Affected if The gorilla/mux router has no authentication middleware configured and the server is network-accessible
  5. Confirm token/sensitive data exposure risk
    If HUD is exposed, verify that engine state or session tokens could be extracted via unauthenticated requests to the HTTP endpoints
    Affected if Unauthenticated access to /proxy handler or engine state endpoints is possible due to missing auth

A user is affected if the Tilt HUD HTTP server is bound to a non-loopback address (0.0.0.0 or external IP), allowing unauthenticated network attackers to access sensitive endpoints and proxy functionality.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade Tilt to version 0.37.4 or later; alternatively, ensure the HUD is bound exclusively to loopback addresses (127.0.0.1/localhost) to prevent network exposure.

Recommended fix High confidence

0.37.4 or later

  1. Identify current Tilt version using `tilt version` or checking deployment manifests
  2. Stop any running Tilt instances
  3. Upgrade Tilt to version 0.37.4 or later by downloading from https://github.com/tilt-dev/tilt/releases
  4. Verify the upgrade was successful by running `tilt version`
  5. If using Tilt in production with HUD bound to non-loopback, ensure the upgrade is deployed to all nodes
Caveat Review release notes for any breaking changes between your current version and 0.37.4; minor version jumps within the 0.x series typically have minimal breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55884 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-55884 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data