Skip to main content
Menu
CVEs

Eclipse Ditto authorization bypass in condition headers

Affects Eclipse Ditto 2.4.0 through 3.9.8 for Thing queries with both a condition and live-channel-condition header, and WoT TD requests with permission filtering off. Fixed in 3.8.15 and 3.9.9.

CVE-2026-129700EUVD-2026-130068Published November 19, 2026, updated

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

Summary

Eclipse Ditto has a flaw in how it checks the `condition` and `live-channel-condition` headers, which lets an authenticated user read Thing fields they are not allowed to read over the network. In some cases the attacker needs no permission on the Thing at all.

Written by a model

Original description

In 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 live-channel-condition headers, which are evaluated against the

full Thing: the READ check of live-channel-condition is skipped when a condition header is also present on Thing query commands (3.0.0 to 3.9.8); both headers are evaluated without any authorization on WoT Thing Description requests (Accept: application/td+json) when WoT TD permission filtering is not active (by default in 3.0.0 to 3.8.14, in 2.4.x with WoT integration enabled, and in 3.9.x with filtering disabled); the condition of live messages and live events is evaluated without a READ check, and of claim messages without any permission (3.1.0 to 3.9.8); and the twin response of a Thing query with a non-matching live-channel-condition is returned without filtering it by the policy (3.0.0 to 3.9.8). This allows an authenticated user to read Thing fields they are not allowed to read, in some cases without any permission on the Thing.

Who should check

Teams running Eclipse Ditto 2.4.0 to 3.9.8 with Things whose policies restrict READ on some fields, or that use live messages, claim messages or WoT Thing Description requests.

“Affected versions: 2.4.0 up to 3.8.14 and 3.9.0 up to 3.9.8.”

github.com

What to do

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

    Thing query commands carrying both a condition and a live-channel-condition header (3.0.0 to 3.9.8) WoT Thing Description requests with WoT TD permission filtering disabled Live messages, claim messages and live events carrying a condition header Thing query with a live-channel-condition that does not match Knowing the ID of the Thing is required
  2. 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-129700 (In 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…), 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-129700 (entry last updated 2026-11-19):
Affected:
- Eclipse Foundation Eclipse Ditto: from 2.4.0, through 3.9.8
Fixed versions: 3.8.15, 3.9.9.
Conditions (all must be true for the bug to be hit):
- Thing query commands carrying both a condition and a live-channel-condition header (3.0.0 to 3.9.8) (source: https://github.com/eclipse-ditto/ditto/security/advisories/GHSA-x88m-jq5c-jpcq)
- WoT Thing Description requests with WoT TD permission filtering disabled (source: https://github.com/eclipse-ditto/ditto/security/advisories/GHSA-x88m-jq5c-jpcq)
- Live messages, claim messages and live events carrying a condition header (source: https://github.com/eclipse-ditto/ditto/security/advisories/GHSA-x88m-jq5c-jpcq)
- Thing query with a live-channel-condition that does not match (source: https://github.com/eclipse-ditto/ditto/security/advisories/GHSA-x88m-jq5c-jpcq)
- Knowing the ID of the Thing is required (source: https://github.com/eclipse-ditto/ditto/security/advisories/GHSA-x88m-jq5c-jpcq)
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.
CISA KEV: CVE-2026-129700 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129700 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-x88m-jq5c-jpcq
- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1390
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/587
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-129700
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-129700"}.

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 5

Questions about CVE-2026-129700

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

Thing fields that a requester is not allowed to read can be disclosed through the condition and live-channel-condition handling in Eclipse Ditto. Knowing the ID of the Thing is required in all cases.

Source: github.com

Which versions are affected by CVE-2026-129700?

Eclipse Ditto: from 2.4.0 through 3.9.8.

Source: cve.now feed data

Am I affected, and how do I check?

The product range is Eclipse Ditto 2.4.0 through 3.9.8, but the advisory names narrower setups: Thing query commands carrying both a condition and a live-channel-condition header (3.0.0 to 3.9.8), and WoT Thing Description requests with WoT TD permission filtering disabled. Live messages, claim messages and live events carrying a condition header, and Thing queries whose live-channel-condition does not match, are also listed. Check the Eclipse Ditto version in use and whether WoT TD permission filtering is disabled.

Source: github.com

How do I fix CVE-2026-129700?

Upgrade to 3.8.15 or 3.9.9, the fixed versions named in the advisory.

Source: github.com

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