Is CVE-2026-55884 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-55884 being exploited in the wild.

How severe is CVE-2026-55884?

Critical severity, with a CVSS score of 4, published 10 July 2026.

Which products and versions are affected?

github.com/tilt-dev/tilt (Go) >= 0.20.8, = 0.20.8, <= 0.37.3, 0.20.8 through 0.37.3.

Is there a fix for CVE-2026-55884?

Yes. github.com/tilt-dev/tilt (Go): upgrade to 0.37.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-55884 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-55884?

Check whether you run github.com/tilt-dev/tilt (Go) or Tilt at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-55884: Tilt HUD missing authentication in HTTP server

Q: Is there a fix for CVE-2026-55884?

Yes. github.com/tilt-dev/tilt (Go): upgrade to 0.37.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-55884 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-55884?

Check whether you run github.com/tilt-dev/tilt (Go) or Tilt at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-55884 · Severity: critical · CVSS 4 · Published 2026-07-10

Tilt, a tool used by developers to manage microservice environments on Kubernetes, contains a security vulnerability in its dashboard (HUD) server. When the dashboard is configured to be accessible over a network rather than just the local machine, it fails to verify the identity of users. This allows an unauthorized person on the same network to view sensitive configuration files, modify development settings, and potentially gain control over the connected Kubernetes resources.

Technologies: github.com/tilt-dev/tilt (Go), Tilt. Vendors: Go, Tilt.

Quick answers

Is CVE-2026-55884 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-55884 being exploited in the wild.
How severe is CVE-2026-55884?: Critical severity, with a CVSS score of 4, published 10 July 2026.
Which products and versions are affected?: github.com/tilt-dev/tilt (Go) >= 0.20.8, <= 0.37.3, SEMVER:introduced=0.20.8,fixed=0.37.4; Tilt >= 0.20.8, <= 0.37.3, 0.20.8 through 0.37.3.
Is there a fix for CVE-2026-55884?: Yes. github.com/tilt-dev/tilt (Go): upgrade to 0.37.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-55884 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-55884?: Check whether you run github.com/tilt-dev/tilt (Go) or Tilt at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/tilt-dev/tilt (Go): upgrade to 0.37.4 or later
```
go get github.com/tilt-dev/tilt@v0.37.4
```

Technical details

The Tilt HUD HTTP server, which utilizes a gorilla/mux router, was found to register several sensitive handlers without authenticating middleware. When the server is bound to a non-loopback address (e.g., via the --host 0.0.0.0 flag), an unauthenticated remote attacker can access endpoints such as /api/view, /api/trigger, and /proxy/*. This allows for the extraction of the full engine state (including session tokens), tampering with Tiltfile arguments, and the invocation of Kubernetes apiserver resources through the token-attaching proxy handler. The vulnerability also included a WebSocket origin check bypass where omitting the Origin header allowed unauthorized access to the full view stream. The issue is resolved in version 0.37.4 by implementing CSRF protection, SameSite=Strict cookies, and mandatory token authentication for sensitive endpoints.

Affected products

tilt-dev Tilt 0.20.8 through 0.37.3

Identifiers

CVE-2026-55884
GHSA-c73q-8xxr-rgqm
GO-2026-5317

Timeline

2026-06-15: patched: Fixes merged into master branch
2026-06-16: advisory: Release v0.37.4 published
2026-07-10: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.