CVE-2025-12548
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 · uneditedA flaw was found in Eclipse Che che-machine-exec. This vulnerability allows unauthenticated remote arbitrary command execution and secret exfiltration (SSH keys, tokens, etc.) from other users' Developer Workspace containers, via an unauthenticated JSON-RPC / websocket API exposed on TCP port 3333.
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 confidenceA critical authentication and authorization bypass exists in Eclipse Che's che-machine-exec component. The JSON-RPC/websocket API listening on TCP port 3333 lacks authentication controls, allowing any unauthenticated attacker to execute arbitrary commands within other users' Developer Workspace containers and exfiltrate sensitive credentials such as SSH keys and tokens.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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.
-
Verify che-machine-exec component is deployedList running containers or pods containing 'che-machine-exec' in their name, or search process list for the che-machine-exec binary/serviceAffected if The che-machine-exec component is running in the environment
-
Confirm port 3333 is listeningRun 'netstat -tlnp | grep 3333' or 'ss -tlnp | grep 3333' on the Che host to verify the JSON-RPC/websocket API port is open and listeningAffected if Port 3333 is open and accepting connections
-
Test unauthenticated API accessAttempt to connect to the websocket endpoint at ws://<che-host>:3333/api/unauthenticated/test without providing any credentials, or use curl to send a JSON-RPC request to http://<che-host>:3333Affected if The API accepts and processes requests without requiring authentication tokens
-
Check for authentication enforcement on websocket endpointReview Che configuration files (usually in /etc/che or the Che operator CR) for authentication settings related to che-machine-exec, or inspect the websocket proxy configurationAffected if No authentication middleware or authorization policy is configured for the che-machine-exec API on port 3333
-
Verify cross-user command execution is possibleSend a JSON-RPC command targeting a different user's workspace container through the unauthenticated endpoint, observing if commands execute in a container belonging to another userAffected if Commands execute in containers belonging to users other than the requester without proper authorization checks
If che-machine-exec is running with port 3333 exposed and the API accepts unauthenticated requests, the environment is affected by this bypass.
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.
From vendor dataImmediately restrict or disable the unauthenticated che-machine-exec API on port 3333. Implement proper authentication and user-level authorization checks on the websocket endpoint to prevent cross-user command execution, and rotate any exposed credentials.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA12.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $16,768.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12548 — 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-2025-12548 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