Skip to main content
Menu
CVEs

Eclipse Ditto field value disclosure in WebSocket and SSE events

CVE-2026-132039Published November 19, 2026, updated

7.1HighCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 3.9.9
Who is exposed
Specific setups only

Summary

Eclipse Ditto, before the fixed release, sends Thing events over WebSocket, Server-Sent Events and connections that can expose field values the subscriber's policy does not allow it to read. An attacker with a low-privilege login and at least partial read access to a Thing can reach this remotely over the network and obtain the values of fields they are not permitted to read whenever events for that Thing are emitted.

Written by a model

Original description

In Eclipse Ditto versions before 3.9.9, Thing events delivered via WebSocket, Server-Sent Events and connections disclose field values which the policy does not allow the subscriber to read. A READ

revoke for one subject of the subscriber's authorization context is not applied when another of its subjects is granted READ. For subscribers with partial READ access, subscription RQL filters, the SSE _context, thing-json placeholders and extra fields are evaluated on the unfiltered event. This allows an authenticated subscriber with at least partial READ access to a Thing to obtain the values of fields it may not read when events for that Thing are emitted.

Who should check

Teams running Eclipse Ditto before 3.9.9 that deliver Thing events over WebSocket, SSE or connections to subscribers with several subjects or partial READ access.

“In Eclipse Ditto versions before 3.9.9”

gitlab.eclipse.org

What to do

  1. Check whether your setup matches what the bug needs.

    Subscriber has several authorization subjects (for example a user subject and a group subject from the same JWT, or a connection target with several subjects). Subscriber has partial READ access to the Thing (partial access events, since 3.9.0). Eclipse Ditto versions before 3.9.9.
  2. Upgrade to a fixed version: 3.9.9.

  3. Workaround: Add the revoke to every subject's policy entry that is granted READ, or disable partial access events (THING_EVENT_PARTIAL_ACCESS_EVENTS_ENABLED=false).

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-132039 (In Eclipse Ditto versions before 3.9.9, Thing events delivered via WebSocket, Server-Sent Events and connections disclose field values…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-132039 (entry last updated 2026-11-19):
Affected:
- Eclipse Foundation Eclipse Ditto: fixed in 3.9.9
Fixed versions: 3.9.9.
Conditions (all must be true for the bug to be hit):
- Subscriber has several authorization subjects (for example a user subject and a group subject from the same JWT, or a connection target with several subjects). (source: https://github.com/eclipse-ditto/ditto/security/advisories/GHSA-3fx4-8jrp-7pqm)
- Subscriber has partial READ access to the Thing (partial access events, since 3.9.0). (source: https://github.com/eclipse-ditto/ditto/security/advisories/GHSA-3fx4-8jrp-7pqm)
- Eclipse Ditto versions before 3.9.9. (source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/605)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
Workaround: Add the revoke to every subject's policy entry that is granted READ, or disable partial access events (THING_EVENT_PARTIAL_ACCESS_EVENTS_ENABLED=false). (source: https://github.com/eclipse-ditto/ditto/security/advisories/GHSA-3fx4-8jrp-7pqm)
CISA KEV: CVE-2026-132039 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132039 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/eclipse-ditto/ditto/security/advisories/GHSA-3fx4-8jrp-7pqm
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/605
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-132039
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132039"}.

Affected versions

cve.now Index

30Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 37 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 4

KindSource
Vendor advisory 2Establishes: Affected and fixed versions.
AdvisoryGitHub · eclipse-ditto/ditto · Advisory GHSA-3fx4-8jrp-7pqm
Linkgitlab.eclipse.org · security/cve-assignment/-/work_items/605
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-132039
RecordNVD · CVE-2026-132039

Questions about CVE-2026-132039

Is CVE-2026-132039 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

Subscribers can read values of Thing fields that the policy does not allow them to read. This happens through events, filters and SSE context, so the policy restriction is not enforced on those channels.

Source: github.com, gitlab.eclipse.org

Which versions are affected by CVE-2026-132039?

Eclipse Ditto: before 3.9.9.

Source: cve.now feed data

Am I affected, and how do I check?

Eclipse Ditto versions before 3.9.9 are affected, and the issue needs a subscriber with several authorization subjects or partial READ access to the Thing, which has existed since 3.9.0. To check a version, look at the Ditto release in use and compare it with 3.9.9; the setup can be checked in the subscriber's policy entries and in the THING_EVENT_PARTIAL_ACCESS_EVENTS_ENABLED setting.

Source: github.com, gitlab.eclipse.org

How do I fix CVE-2026-132039?

Upgrade Eclipse Ditto to 3.9.9, which is the fixed version named by the advisory. If an upgrade is not possible yet, use the workaround listed under no-patch.

Source: github.com, gitlab.eclipse.org

No corrections so far. Something wrong on this page? Report an error.