What is CVE-2026-42283?

CVE-2026-42283 is a high-severity missing authentication for critical function vulnerability in github.com/loft-sh/devspace (go), affecting versions = 6.3.20. It is fixed in 6.3.21. A critical operation is accessible without requiring any authentication.

How severe is CVE-2026-42283?

CVE-2026-42283 has a CVSS score of 7.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/loft-sh/devspace are affected by CVE-2026-42283?

github.com/loft-sh/devspace (go) versions = 6.3.20 is affected.

Is there a fix for CVE-2026-42283?

Yes. CVE-2026-42283 is fixed in 6.3.21. Upgrade to this version or later.

Is CVE-2026-42283 exploitable, and should I be worried?

Whether CVE-2026-42283 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-42283 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-42283?

Upgrade github.com/loft-sh/devspace to 6.3.21 or later.

CVE-2026-42283 in github.com/loft-sh/devspace | Intelligent Application Security

Summary

Description

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 allows an attacker to access:

/api/logs to stream real-time pod logs
/api/enter to open an interactive shell inside the running pod
/api/command to execute pre-defined pipeline commands

Resources

gorilla/websocket CheckOrigin documentation

Installation Options

Devspace is no longer publishing to NPM or Yarn, please continue to use our other installation methods to get updates in the future, including this patch.

Credit

DevSpace thanks @b0b0haha for finding and reporting this vulnerability.

Impact

A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.

CVE-2026-42283 has a CVSS score of 7.7 (High). The vector is requires local access, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.3.21); upgrading removes the vulnerable code path.

Affected versions

github.com/loft-sh/devspace (= 6.3.20)

Security releases

github.com/loft-sh/devspace → 6.3.21 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Versions 6.3.21 and above are patched.

Frequently Asked Questions

What is CVE-2026-42283? CVE-2026-42283 is a high-severity missing authentication for critical function vulnerability in github.com/loft-sh/devspace (go), affecting versions = 6.3.20. It is fixed in 6.3.21. A critical operation is accessible without requiring any authentication.
How severe is CVE-2026-42283? CVE-2026-42283 has a CVSS score of 7.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of github.com/loft-sh/devspace are affected by CVE-2026-42283? github.com/loft-sh/devspace (go) versions = 6.3.20 is affected.
Is there a fix for CVE-2026-42283? Yes. CVE-2026-42283 is fixed in 6.3.21. Upgrade to this version or later.
Is CVE-2026-42283 exploitable, and should I be worried? Whether CVE-2026-42283 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-42283 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-42283? Upgrade github.com/loft-sh/devspace to 6.3.21 or later.

Other vulnerabilities in github.com/loft-sh/devspace

CVE-2020-15391