# CVE-2026-132039: In Eclipse Ditto versions before 3.9.9, Thing events delivered via WebSocket, Server-Sent Events and connections disclose field values which


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026

## What is CVE-2026-132039?

CVE-2026-132039 is a high-severity vulnerability in Eclipse Ditto, published on 19 Nov 2026. 

### Official 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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-132039?


## How do I fix CVE-2026-132039?

Upgrade Eclipse Ditto to 3.9.9 or later. The advisory says that version fixes it.

## Is CVE-2026-132039 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-132039 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-132039 and fix it if it is affected.

What it is: CVE-2026-132039 is a high-severity vulnerability in Eclipse Ditto, published on 19 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-132039 exists.

Affected product: Eclipse Ditto. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-132039/ (Markdown: https://insights.sbomify.com/CVE-2026-132039/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-132039
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-132039
- OSV: https://osv.dev/vulnerability/CVE-2026-132039

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-132039/
Summaries are generated and may contain mistakes; the official description above is the record.
