Vulnerability in github.com/tilt-dev/tilt (CVE-2026-55883)
Summary
Vulnerability in github.com/tilt-dev/tilt (CVE-2026-55883). Risk of unauthorized operations or information disclosure. Exploitable via Origin. Mitigation: upgrade to 0.37.4 or later.
Original description
The description as published by the source.
Tilt defines dev environments as code for microservice apps on Kubernetes. From 0.24.0 through 0.37.3, the Tilt HUD WebSocket at /ws/view is gated by a CSRF token, but the token is served by the unauthenticated /api/websocket_token endpoint and the upgrader accepts clients that omit an Origin header. When the HUD is network-exposed, an attacker who can reach the listener can open the HUD WebSocket and receive the full view stream, including session state, Tiltfile contents, resource statuses, and continued updates. This issue is fixed in version 0.37.4.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55883 has been found in github.com/tilt-dev/tilt.
Attackers can target a specific entry point like Origin over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/tilt-dev/tilt to 0.37.4 or later.
If unsure, ask your IT team or search "github.com/tilt-dev/tilt CVE-2026-55883" on the vendor's site.
CVE-2026-55883 (github.com/tilt-dev/tilt) — CWE-345
Attack surface: Origin / csrf / websocketCSRFToken / WebsocketToken
Patched: 0.37.4 — apply immediately
Workaround: Use the default loopback bind (omit --host, unset TILT_HOST).
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-345) exists in github.com/tilt-dev/tilt. Attackers reach the vulnerable code path via Origin.
Check the vendor advisory for the affected versions of github.com/tilt-dev/tilt. Attack surface: Origin / csrf / websocketCSRFToken / WebsocketToken.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.37.4.
Workaround: Use the default loopback bind (omit --host, unset TILT_HOST).
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/tilt-dev/tilt' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/tilt-dev/tilt' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/tilt-dev/tiltを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Use the default loopback bind (omit `--host`, unset `TILT_HOST`).パッチが適用されるまでの応急処置として、Use the default loopback bind (omit
--host, unsetTILT_HOST). を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade github.com/tilt-dev/tilt to 0.37.4ステージング環境で 0.37.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com