CVE-2026-84197
Last modified
CVE-2026-84197 is a critical-severity vulnerability rated 9.2/10 on the CVSS scale. 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. EPSS estimates a 0.20% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Eclipse Foundation | Eclipse Ditto | >= 2.0.0, < 3.8.1; >= 3.9.0, < 3.9.1 |
| Eclipse Foundation | Eclipse Ditto | >= 1.0.0, <= 2.1.0 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-84197?
How severe is CVE-2026-84197?
How do I fix CVE-2026-84197?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-84191LibreNMS before 26.5.0 contains stored cross-site scripting …6.1
- CVE-2026-84192LibreNMS before 26.3.1 contains a stored cross-site scriptin…7.1
- CVE-2026-84193LibreNMS through 26.2.0 contains a stored cross-site scripti…5.8
- CVE-2026-84194LibreNMS versions >= 23.10.0 and < 26.2.0 (fixed in 26.4.0) …8.6
- CVE-2026-84195Kyverno before 1.16.4 automatically attaches the admission c…7.7
- CVE-2026-84196Kyverno before 1.18.0 contains a server-side request forgery…7.7
- CVE-2026-84199Kyverno before 1.16.2 contains a server-side request forgery…7.7
- CVE-2026-8420The BLOGCHAT Chat System plugin for WordPress is vulnerable …6.1
- CVE-2026-84200Kyverno versions v1.9.0 through v1.12.7 contain a policy exc…9
- CVE-2026-84201appium-mcp-server through 0.1.61 fails to validate or normal…7.1
- CVE-2026-84202ModelScope uses PyYAML's unsafe yaml.Loader to parse model c…8.8
- CVE-2026-84203Memos versions 0.26.0 through 0.30.0 fail to revoke refresh …8.1
Are you affected by CVE-2026-84197?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
