CVE-2026-55883: CWE-345: Insufficient Verification of Data Authenticity in tilt-dev tilt
Tilt versions from 0.24.0 up to 0.37.3 have a vulnerability in the Tilt HUD WebSocket at /ws/view. The WebSocket is protected by a CSRF token served by an unauthenticated endpoint, and the upgrader accepts clients without an Origin header. This allows an attacker with network access to the HUD WebSocket to receive sensitive information including session state, Tiltfile contents, and resource statuses. The issue is fixed in version 0.37.4.
AI Analysis
Technical Summary
Tilt, a tool for defining dev environments as code on Kubernetes, versions 0.24.0 through 0.37.3 expose a vulnerability (CWE-345) due to insufficient verification of data authenticity in the Tilt HUD WebSocket at /ws/view. The CSRF token protecting the WebSocket is obtained from an unauthenticated endpoint (/api/websocket_token), and the WebSocket upgrader accepts connections without verifying the Origin header. When the HUD is exposed on the network, an attacker able to reach the listener can open the WebSocket and receive the full view stream, including sensitive session state, Tiltfile contents, resource statuses, and ongoing updates. This vulnerability is addressed in version 0.37.4.
Potential Impact
An attacker with network access to the Tilt HUD WebSocket can bypass CSRF protections and receive sensitive internal data streams, including session state and configuration files. This exposure could lead to information disclosure impacting confidentiality of the development environment and potentially enabling further attacks.
Mitigation Recommendations
Upgrade Tilt to version 0.37.4 or later, where this vulnerability is fixed. Until then, avoid exposing the Tilt HUD WebSocket on untrusted networks to prevent unauthorized access. Patch status is not explicitly stated as 'official-fix' in the vendor advisory, but the description confirms the issue is fixed in 0.37.4.
CVE-2026-55883: CWE-345: Insufficient Verification of Data Authenticity in tilt-dev tilt
Description
Tilt versions from 0.24.0 up to 0.37.3 have a vulnerability in the Tilt HUD WebSocket at /ws/view. The WebSocket is protected by a CSRF token served by an unauthenticated endpoint, and the upgrader accepts clients without an Origin header. This allows an attacker with network access to the HUD WebSocket to receive sensitive information including session state, Tiltfile contents, and resource statuses. The issue is fixed in version 0.37.4.
CVSS v4.0
Score 8.3high
Affected software
pkg:github/tilt-dev/tiltRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Tilt, a tool for defining dev environments as code on Kubernetes, versions 0.24.0 through 0.37.3 expose a vulnerability (CWE-345) due to insufficient verification of data authenticity in the Tilt HUD WebSocket at /ws/view. The CSRF token protecting the WebSocket is obtained from an unauthenticated endpoint (/api/websocket_token), and the WebSocket upgrader accepts connections without verifying the Origin header. When the HUD is exposed on the network, an attacker able to reach the listener can open the WebSocket and receive the full view stream, including sensitive session state, Tiltfile contents, resource statuses, and ongoing updates. This vulnerability is addressed in version 0.37.4.
Potential Impact
An attacker with network access to the Tilt HUD WebSocket can bypass CSRF protections and receive sensitive internal data streams, including session state and configuration files. This exposure could lead to information disclosure impacting confidentiality of the development environment and potentially enabling further attacks.
Mitigation Recommendations
Upgrade Tilt to version 0.37.4 or later, where this vulnerability is fixed. Until then, avoid exposing the Tilt HUD WebSocket on untrusted networks to prevent unauthorized access. Patch status is not explicitly stated as 'official-fix' in the vendor advisory, but the description confirms the issue is fixed in 0.37.4.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-17T16:59:42.759Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a516c2d68715ace43438254
Added to database: 07/10/2026, 22:03:25 UTC
Last enriched: 07/20/2026, 19:19:14 UTC
Last updated: 08/24/2026, 10:52:10 UTC
Views: 74
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.