Skip to content
Applications

CVE-2026-55884

9.2
Critical
EPSS 0.50%Patch availableJul 11, 2026

Unauthenticated remote access to Tilt HUD enables token theft and execution of developer-defined actions.

common questions

Is CVE-2026-55884 being exploited?

Not confirmed. CVE-2026-55884 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.50% probability of exploitation in the next 30 days.

How severe is CVE-2026-55884?

CVE-2026-55884 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-55884?

Yes. A fix has been recorded for CVE-2026-55884. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-55884 affect?

CVE-2026-55884 affects Tilt (HUD) versions 0.20.8–0.37.3, Tilt HUD HTTP server bound to non-loopback addresses, Kubernetes dev environments using Tilt with HUD exposed. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-55884?

Upgrade Tilt to >=0.37.4 or bind HUD to localhost and restrict network access; rotate exposed tokens.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Tilt (HUD) versions 0.20.8–0.37.3Tilt HUD HTTP server bound to non-loopback addressesKubernetes dev environments using Tilt with HUD exposed
impact

Unauthenticated attacker can read session tokens, tamper Tiltfile args, trigger developer resources, and call Kubernetes API via token-attaching /proxy (remote code/command execution).

action required

Immediate action required

affected versions
tilt-dev tilt
  • affected>= 0.20.8 and < 0.37.4

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free