Skip to main content
Menu
CVEs

Eclipse Ditto authorization bypass in policy enforcers

CVE-2026-129702EUVD-2026-130072Published November 19, 2026, updated

2.3LowCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 3.8.15, 3.9.9
Who is exposed
Not reported

Summary

Eclipse Ditto's policy enforcers can let a revoke fail to override a grant in multi-permission and partial permission checks. A remote attacker who has logged in with low privileges can learn that some Things and Policies exist and receive their metadata without readable content, and applications that rely on the check permissions API may grant access the policy denies.

Written by a model

Original description

In Eclipse Ditto versions before 3.8.15 and 3.9.0 to 3.9.8, the policy enforcers do not let a revoke win over a grant in two kinds of permission checks. Checks of several permissions at once compare the highest grant weight with the highest revoke weight across all requested permissions instead of per permission, so the "check permissions" API (POST /api/2/checkPermissions, available since 3.7.0) can report a set of permissions as granted although one of them is revoked. Partial permission checks, which authorize retrieving Things and Policies and determine the receivers of events, count a grant on a sub-resource although the same permission is revoked on that sub-resource for another subject of the same authorization context (or, with the memory-optimized policy evaluator, for the same subject). A requester can thereby learn about the existence of Things and Policies and receive metadata without any readable content, and an application relying on the check permissions result may grant access the policy denies. The content of retrieved Things and Policies is still filtered correctly, and modifications are not affected.

What to do

Upgrade to a fixed version: 3.8.15, 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-129702 (Eclipse Ditto policy enforcers ignore revokes in multi-permission and partial permission checks), 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-129702 (entry last updated 2026-11-19):
Affected:
- Eclipse Foundation Eclipse Ditto: fixed in 3.8.15; from 3.9.0, fixed in 3.9.9
Fixed versions: 3.8.15, 3.9.9.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129702 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129702 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-73pw-g56w-95h8
- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1391
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/588
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-129702
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-129702"}.

Affected versions

cve.now Index

20Pof 100 · provisional · methodology v3
  • 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

  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 5

Questions about CVE-2026-129702

Is CVE-2026-129702 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-129702?

Eclipse Ditto: before 3.8.15; from 3.9.0 before 3.9.9.

Source: cve.now feed data

How do I fix CVE-2026-129702?

Upgrade to a fixed version: 3.8.15, 3.9.9.

Source: cve.now feed data

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