devspace-sh devspace up to 6.3.20 UI Server WebSocket missing authentication

Summaryinfo

A vulnerability, which was classified as critical, has been found in devspace-sh devspace up to 6.3.20. This issue affects some unknown processing of the component UI Server WebSocket. The manipulation leads to missing authentication. This vulnerability is uniquely identified as CVE-2026-42283. Local access is required to approach this attack. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in devspace-sh devspace up to 6.3.20. This issue affects an unknown functionality of the component UI Server WebSocket. The manipulation with an unknown input leads to a missing authentication vulnerability. Using CWE to declare the problem leads to CWE-306. The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

DevSpace is a client-only developer tool for cloud-native development with Kubernetes. Prior to 6.3.21, DevSpace's UI server WebSocket accepts connections from all origins by default, and therefore several endpoints are exposed via this WebSocket. When a developer runs the DevSpace UI and at the same time uses a browser to access the internet, a malicious website they visit can use their browser to establish a cross-origin WebSocket connection to ws://127.0.0.1:8090. This vulnerability is fixed in 6.3.21.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-42283 since 04/26/2026. The exploitation is known to be difficult. An attack has to be approached locally. Neither technical details nor an exploit are publicly available.

Upgrading to version 6.3.21 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-30319). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• devspace-sh

Name

• devspace

Version

• 6.3.0
• 6.3.1
• 6.3.2
• 6.3.3
• 6.3.4
• 6.3.5
• 6.3.6
• 6.3.7
• 6.3.8
• 6.3.9
• 6.3.10
• 6.3.11
• 6.3.12
• 6.3.13
• 6.3.14
• 6.3.15
• 6.3.16
• 6.3.17
• 6.3.18
• 6.3.19
• 6.3.20

Website

• Product: https://github.com/devspace-sh/devspace/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion