Skip to main content
Menu
CVEs

Eclipse Ditto authorization bypass in JSON merge patch on Things

CVE-2026-129699EUVD-2026-130071Published November 19, 2026, updated

7.1HighCNA
Exploited
Proof of concept public, per CISA
Fix
See vendor advisory
Who is exposed
Specific setups only

Summary

Eclipse Ditto's authorization check for JSON merge patch commands on Things skips fields that are deleted or set to an empty object. Over the network and without user interaction, an authenticated user with WRITE permission on any part of a Thing can delete other attributes, features, or the Thing's definition, or overwrite or create fields as empty objects, including parts the policy does not grant WRITE on.

Written by a model

Original description

In 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 PATCH / Ditto Protocol merge) does not check permissions for fields

deleted or set to an empty object by the patch: fields with a null value or an empty object value ({}) are skipped by the check, and Ditto's regex-based key deletion with the documented {{ ~<regex>~ }} syntax is not recognized as a deletion. An authenticated user with WRITE permission on any part of a Thing can therefore delete other attributes, features and the definition of that Thing, or overwrite or create fields as empty objects, including parts the policy revokes or never grants WRITE on.

-->

Who should check

Teams running Eclipse Ditto 2.0.0 to 3.8.14 or 3.9.0 to 3.9.8 where some subjects have WRITE on only part of a Thing, such as 'write everything except' or 'only these fields' policies

“Impacted are Eclipse Ditto deployments where subjects have WRITE permission on only a part of a Thing, e.g.:”

github.com

What to do

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

    Eclipse Ditto versions 2.0.0 to 3.8.14 or 3.9.0 to 3.9.8 The subject holds WRITE permission on some part of a Thing The regex-key variant applies only to versions 3.5.5 and later
  2. Workaround: The checked facts do not describe a workaround. Limiting which subjects hold WRITE permission on Things is the only mitigation the facts point to, and the advisory should be checked for the vendor's guidance.

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-129699 (In 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…), 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-129699 (entry last updated 2026-11-19):
Affected:
- Eclipse Foundation Eclipse Ditto: from 2.0.0, through 3.8.14; from 3.9.0, through 3.9.8
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Eclipse Ditto versions 2.0.0 to 3.8.14 or 3.9.0 to 3.9.8 (source: https://github.com/eclipse-ditto/ditto/security/advisories/GHSA-5hh9-qp4v-6f56)
- The subject holds WRITE permission on some part of a Thing (source: https://github.com/eclipse-ditto/ditto/security/advisories/GHSA-5hh9-qp4v-6f56)
- The regex-key variant applies only to versions 3.5.5 and later (source: https://github.com/eclipse-ditto/ditto/security/advisories/GHSA-5hh9-qp4v-6f56)
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-129699 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129699 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-5hh9-qp4v-6f56
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/589
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-129699
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-129699"}.

Affected versions

cve.now Index

35Pof 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 patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 42 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 4

KindSource
Vendor advisory 2Establishes: Affected and fixed versions.
AdvisoryGitHub · eclipse-ditto/ditto · Advisory GHSA-5hh9-qp4v-6f56
Linkgitlab.eclipse.org · security/cve-assignment/-/work_items/589
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-129699
RecordNVD · CVE-2026-129699

Questions about CVE-2026-129699

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

An authenticated user with WRITE permission on any part of a Thing can use a JSON merge patch command to delete other parts of that Thing, including attributes, features and the Thing definition. The user can also overwrite or create fields as empty objects, including parts the policy does not grant them WRITE on.

Source: github.com

Which versions are affected by CVE-2026-129699?

Eclipse Ditto: from 2.0.0 through 3.8.14; from 3.9.0 through 3.9.8.

Source: cve.now feed data

Am I affected, and how do I check?

The advisory lists Eclipse Ditto versions 2.0.0 up to 3.8.14 and 3.9.0 up to 3.9.8. The regex-key variant applies only to versions 3.5.5 and later. To check a deployment, look up the Eclipse Ditto version it runs and compare it against these ranges.

Source: github.com

How do I fix CVE-2026-129699?

The checked facts do not name a fixed version or vendor patch identifiers, so no upgrade target can be confirmed from them. Consult the Eclipse Ditto advisory for the fix details.

Source: github.com

What if there's no patch?

The checked facts do not describe a workaround. Limiting which subjects hold WRITE permission on Things is the only mitigation the facts point to, and the advisory should be checked for the vendor's guidance.

Source: github.com

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