Eclipse Ditto authorization bypass in resolved policy view
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 3.9.9
- Who is exposed
- Not reported
Summary
Eclipse Ditto's resolved policy view can expose the contents of imported, namespace-root and referenced policy entries that the caller is not allowed to read. A remote user with low-privilege login and READ on a policy can use this to see subjects, resources and granted or revoked permissions in entries that are hidden from them, including entries hidden by explicit revokes.
Written by a model
Original description
In Eclipse Ditto versions 3.9.0 to 3.9.8, the resolved policy view (GET /api/2/policies/{policyId}?policy-view=resolved) does not restrict merged policy content to what the caller may read in the policy it originates from. Imported and namespace-root entries are returned in full as soon as the caller may read any part of them in the source policy, entries of transitive imports and of the imports of namespace-root policies are only checked against the intermediate policy, and content copied into an entry by references, also from another entry of the same policy, is not checked against the referenced entry. An authenticated caller with READ on a policy can therefore read subjects, resources and granted/revoked permissions of policy entries that are hidden from them, including by explicit revokes, when reading the originating policy directly.
What to do
Upgrade to a fixed version: 3.9.9.
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-129916 (Eclipse Ditto resolved policy view discloses non-readable content of imported, namespace root and referenced policy entries), 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-129916 (entry last updated 2026-11-19):
Affected:
- Eclipse Foundation Eclipse Ditto: from 3.9.0, fixed in 3.9.9
Fixed versions: 3.9.9.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129916 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129916 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://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1393
- https://github.com/eclipse-ditto/ditto/security/advisories/GHSA-mx63-5cwx-v3pr
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/590
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-129916
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-129916"}.Affected versions
- Eclipse Foundation Eclipse DittoFrom 3.9.0 · fixed in 3.9.9
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity2.3/10CVSS 2.3
- No patch0/5No signal
What would change the score
- Would score about 60 if added to CISA KEV
- Would score about 55 if CISA's SSVC rates exploitation active
- Would score about 39 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 3Establishes: Affected and fixed versions. | |
| Advisory | GitHub · eclipse-ditto/ditto · Advisory GHSA-mx63-5cwx-v3pr |
| Link | gitlab.eclipse.org · security/vulnerability-reports/-/work_items/1393 |
| Link | gitlab.eclipse.org · security/cve-assignment/-/work_items/590 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129916 |
| Record | NVD · CVE-2026-129916 |
Questions about CVE-2026-129916
Is CVE-2026-129916 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
Which versions are affected by CVE-2026-129916?
Eclipse Ditto: from 3.9.0 before 3.9.9.
Source: cve.now feed data
How do I fix CVE-2026-129916?
Upgrade to a fixed version: 3.9.9.
Source: cve.now feed data
Related
- CVE-2026-84197In 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
- CVE-2026-120753Eclipse Ditto gateway accepts `x-ditto-pre-authenticated` from a URL query parameter, allowing unauthenticated subject impersonation…
- CVE-2026-82958In Eclipse Ditto versions [1.3.0, 3.9.6], the ImplicitThingCreationMessageMapper of the connectivity service builds a CreateThing command…
- CVE-2026-129699In Eclipse Ditto versions 2.0.0 to 3.8.14 and 3.9.0 to 3.9.8, the authorization check for JSON merge patch commands on Things (HTTP…
- CVE-2026-129700In Eclipse Ditto versions 2.4.0 to 3.9.8, Thing fields a requester is not allowed to read can be disclosed through the `condition` and…
- CVE-2026-132039In Eclipse Ditto versions before 3.9.9, Thing events delivered via WebSocket, Server-Sent Events and connections disclose field values…
No corrections so far. Something wrong on this page? Report an error.