CVE-2026-84197

published 8 Sep 2026 · updated 9 Sep 2026

In Eclipse Ditto's Node.js JavaScript client, all released versions of @eclipse-ditto/ditto-javascript-client-node from 2.0.0 to 3.9.0 and…

9.2CriticalCVSS 9.2EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 3.8.1 and 3.9.1.

In Eclipse Ditto's Node.js JavaScript client, all released versions of @eclipse-ditto/ditto-javascript-client-node from 2.0.0 to 3.9.0 and of its predecessor package @eclipse-ditto/ditto-javascript-client-node_1.0 from 1.0.0 to 2.1.0, the WebSocket transport hard-codes rejectUnauthorized: false when creating the underlying ws WebSocket. Certificate chain and hostname validation are therefore disabled for every wss:// connection, and no builder option, constructor argument or environment variable lets an application turn validation back on. An attacker in a position to intercept the connection can present an arbitrary certificate, complete the TLS handshake, read the credentials that the configured authentication provider sends in the Authorization header of the WebSocket upgrade request, and read, alter or inject Ditto Protocol messages for the lifetime of the connection. The Java client, the browser/DOM JavaScript client and the HTTP transport of the Node.js client are not affected.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Eclipse Foundation>=1.0.0 <=2.1.0, >=2.0.0 <3.8.1, >=3.9.0 <3.9.13.8.1, 3.9.1

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-84197 severity on Zeptric[![CVE-2026-84197](https://zeptric.io/badge/cve/CVE-2026-84197.svg)](https://zeptric.io/cve/CVE-2026-84197)