CVE-2026-42283
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDevSpace 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceDevSpace UI server's WebSocket endpoint on localhost:8090 accepts connections from all origins by default, enabling malicious websites visited by a developer to establish cross-origin WebSocket connections and interact with exposed internal endpoints.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 6.3.20CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed DevSpace versionRun the DevSpace version command (e.g., `devspace version` or check the installed package version) to confirm the exact version numberAffected if Version is exactly 6.3.20
-
Verify DevSpace UI server is runningCheck if the DevSpace UI server process is active and listening on port 8090 (e.g., using `netstat` or `ss` to query port 8090, or check process list for DevSpace UI)Affected if DevSpace UI server is running and port 8090 is in use
-
Confirm WebSocket endpoint accessibilityAttempt to access the WebSocket endpoint at ws://localhost:8090 (e.g., using a WebSocket client or curl with upgrade headers) to verify the service is reachableAffected if WebSocket endpoint on port 8090 responds to connection requests
-
Test cross-origin WebSocket behaviorSend a WebSocket connection request with an arbitrary Origin header (e.g., Origin: http://malicious-site.com) to the localhost:8090 endpoint and verify whether the server accepts the connection without rejecting itAffected if The server accepts the WebSocket connection with a mismatched or arbitrary Origin header, indicating origin validation is not enforced
User is affected if DevSpace version is exactly 6.3.20 and the UI server WebSocket endpoint on port 8090 accepts connections from arbitrary origins without validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade DevSpace to version 6.3.21 or later, which implements proper origin validation on the WebSocket connection.
6.3.21
- 1. Check the currently installed DevSpace version using: devspace version
- 2. Upgrade DevSpace to version 6.3.21 or later using the appropriate installation method (e.g., npm install -g devspace, brew upgrade, or download from the official releases)
- 3. Verify the upgrade was successful by running: devspace version
- 4. Restart the DevSpace UI server to ensure the patched version is running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42283 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-42283 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data