Security readout for executives and security teams
Plain-English summary
The affected Node.js clients silently trust any certificate for secure WebSocket connections. An attacker able to intercept network traffic could impersonate the Ditto endpoint, steal authentication credentials, and read or manipulate messages. The supplied sources rate this critical, but provide no evidence of active exploitation.
Executive priority
Treat as an urgent remediation and credential-exposure review for affected production deployments. Prioritize systems carrying sensitive device data, commands, or privileged credentials, especially across untrusted networks. Do not infer compromise solely from package presence, but do not defer action because exploitation has not been publicly reported.
Technical view
The WebSocket transport hard-codes rejectUnauthorized: false, disabling certificate-chain and hostname validation for wss:// connections without a supported override. This enables an on-path attacker to complete TLS using an arbitrary certificate, capture the WebSocket Authorization header, and alter Ditto Protocol traffic. Node.js HTTP transport, Java clients, and browser/DOM JavaScript clients are unaffected.
Likely exposure
Exposure requires the affected Node.js package and its WebSocket transport using wss://. The stated affected ranges are @eclipse-ditto/ditto-javascript-client-node 2.0.0–3.9.0 and predecessor @eclipse-ditto/ditto-javascript-client-node_1.0 1.0.0–2.1.0. Risk is greatest across untrusted or interceptable networks.
Exploitation context
Exploitation requires an attacker positioned to intercept the client connection. No privileges or user interaction are required after obtaining that position. The bundle marks the CVE as absent from KEV and provides no cited evidence of exploitation in the wild; this does not prove exploitation has never occurred.
Researcher notes
This is improper certificate and hostname validation, mapped to CWE-295, CWE-297, and CWE-300. The defect is unconditional in the described WebSocket construction path and reportedly cannot be reversed through configuration. The supplied material does not identify a patched version, workaround, proof of concept, or observed exploitation campaign.
Mitigation direction
- Identify deployments using either affected Node.js package and the WebSocket transport.
- Check Eclipse guidance for a corrected release or supported remediation; none is named in the supplied sources.
- Avoid affected wss:// connections until certificate validation can be restored through a vendor-supported solution.
- Restrict network paths and endpoint access to reduce opportunities for connection interception.
- After remediation, rotate credentials that may have traversed affected WebSocket connections.
Validation and detection
- Review dependency manifests and lockfiles for both affected package names and stated version ranges.
- Confirm whether each deployment uses Node.js WebSocket transport rather than unaffected HTTP, Java, or browser clients.
- In an authorized test environment, verify wss:// connections reject untrusted certificates and hostname mismatches.
- Review relevant credential and Ditto message activity for unexpected use or modification.
- Confirm deployed remediation against current Eclipse advisory guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-295: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-297: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-300: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-84197 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.2 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N——eclipseVulnerability scoring details
Base CVSS 4.0 score
9.2CriticalVector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/660CVE reference, eclipse
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Certificate Validation
Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Validation of Certificate with Host Mismatch
Improper Validation of Certificate with Host Mismatch represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Channel Accessible by Non-Endpoint
Channel Accessible by Non-Endpoint represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.