dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-55882

HIGH · 8.3 CVSS v4.0 Published 2026-07-10
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
92/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.19.5 through 0.37.3, the Tilt HUD server mounts Go net/http/pprof handlers under /debug with no access control. When the HUD or apiserver listener is network-exposed, an unauthenticated caller can read process memory through /debug/pprof/heap and /debug/pprof/goroutine, including session and apiserver tokens, and degrade performance through /debug/pprof/profile or /debug/pprof/trace. 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's HUD server exposes Go net/http/pprof debugging handlers at /debug/pprof/* without any authentication. When network-exposed, unauthenticated attackers can read process memory (including session and apiserver tokens) via /debug/pprof/heap and /debug/pprof/goroutine, and cause denial-of-service via /debug/pprof/profile and /debug/pprof/trace.

MitigationUpdate Tilt to version 0.37.4 or later. Additionally, ensure the HUD and apiserver listeners are not network-exposed to the public internet.

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:N/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. Check installed Tilt version
    Run 'tilt version' or 'tiltctl version' to get the running Tilt version number
    Affected if Version is 0.19.5, 0.19.6, 0.19.7, 0.19.8, 0.20.0 through 0.37.3 (any version in the range 0.19.5 to 0.37.3 inclusive)
  2. Verify HUD network exposure
    Check Tilt startup flags or config for HUD host binding; look for --hud-host, TILT_HUD_HOST env var, or equivalent config setting; common values are 'localhost' (safe) versus '0.0.0.0' or an external IP (exposed)
    Affected if HUD is bound to 0.0.0.0 or any non-localhost IP address, making it reachable from the network
  3. Verify apiserver network exposure
    Check Tilt startup flags or config for apiserver listener binding; look for --api-host, TILT_API_HOST, or apiserver-related flags; determine if the listener accepts connections from non-localhost addresses
    Affected if Apiserver listener is bound to a network-accessible address (0.0.0.0 or external IP) rather than localhost only
  4. Test pprof endpoint accessibility
    If HUD or apiserver is network-exposed, attempt HTTP requests to /debug/pprof/heap, /debug/pprof/goroutine, /debug/pprof/profile, or /debug/pprof/trace on the exposed host and port
    Affected if Any of these endpoints return memory profiling data, goroutine dumps, or trace output without requiring authentication

Environment is affected if Tilt version is between 0.19.5 and 0.37.3 AND either the HUD or apiserver is network-exposed, allowing unauthenticated access to /debug pprof endpoints.

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

Update Tilt to version 0.37.4 or later. Additionally, ensure the HUD and apiserver listeners are not network-exposed to the public internet.

Recommended fix High confidence

0.37.4

  1. 1. Identify the current Tilt version by running `tilt version` or checking your deployment manifests
  2. 2. If running a version between 0.19.5 and 0.37.3, plan an upgrade to version 0.37.4 or later
  3. 3. For Tilt installations via brew: run `brew upgrade tilt` or `brew install [email protected]`
  4. 4. For manual installations: download the v0.37.4 release from the Tilt GitHub releases page and replace the existing binary
  5. 5. For Kubernetes deployments: update the Tilt image tag in your deployment configuration to `v0.37.4` or later
  6. 6. Restart the Tilt HUD server and apiserver to apply the updated version
  7. 7. Verify the upgrade was successful by running `tilt version` and confirming it shows 0.37.4 or higher
Caveat Review the Tilt v0.37.4 release notes for any breaking changes between your current version and 0.37.4; minor version upgrades typically have minimal breaking changes but test in a non-production environment first

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55882 — 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-55882 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