Information Disclosure in github.com/loft-sh/devspace (CVE-2026-42283)
Summary
Vulnerability in github.com/loft-sh/devspace (CVE-2026-42283). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 6.3.21 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database 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-42283 has been found in github.com/loft-sh/devspace.
Successful exploitation can lead to full system takeover. CVSS score: 7.7/10.
What to do: upgrade github.com/loft-sh/devspace to 6.3.21 or later.
If unsure, ask your IT team or search "github.com/loft-sh/devspace CVE-2026-42283" on the vendor's site.
CVE-2026-42283 (github.com/loft-sh/devspace) — CWE-200 / CVSS v3 7.7
Attack vector: local / unauthenticated
Patched: 6.3.21 — apply immediately
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.
Information disclosure (CWE-200) exists in github.com/loft-sh/devspace.
Check the vendor advisory for the affected versions of github.com/loft-sh/devspace.
Severity: High (CVSS 7.7/10). Successful exploitation can lead to full system takeover.
Update to 6.3.21.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/loft-sh/devspace' . 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/loft-sh/devspace' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/loft-sh/devspaceを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/loft-sh/devspace to 6.3.21ステージング環境で 6.3.21 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-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
- web github.com