Skip to main content
Menu
CVEs

Eclipse Ditto authentication bypass in gateway

Affects Eclipse Ditto 1.1.0 through 3.9.8 with gateway pre-authentication enabled, including the default Helm chart setup with global.jwtOnly=false. Fixed in 3.9.9 and 3.8.15.

CVE-2026-120753EUVD-2026-130290Published November 19, 2026, updated

9.1CriticalCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 3.9.9, 3.8.15
Who is exposed
Default setups

Summary

Eclipse Ditto's gateway can accept a caller-supplied pre-authenticated subject through an undocumented URL query parameter, so a remote attacker who doesn't need to log in can act as any chosen policy subject. That lets them read and modify Things and Policies with the permissions of that subject.

Written by a model

Original description

In Eclipse Ditto versions 1.1.0 to 3.9.8, when pre-authentication is enabled, the gateway service accepts the pre-authenticated subject not only from the x-ditto-pre-authenticated HTTP header set by a trusted reverse proxy, but also from an undocumented x-ditto-pre-authenticated URL query parameter that a client can set. A reverse proxy that only overwrites the header therefore does not stop clients from supplying their own subject. With the default configuration of the Ditto Helm chart (global.jwtOnly: false, which implicitly enables pre-authentication), the bundled nginx skips HTTP Basic authentication for any request with an Authorization: Bearer header and forwards it without the pre-authentication header. An unauthenticated remote attacker can send an invalid Bearer token together with the query parameter to authenticate as any chosen policy subject. Pre-authentication succeeds before the JWT is validated, so the attacker can read and modify Things and Policies with that subject's permissions. As a mitigation, disable pre-authentication in the gateway (ENABLE_PRE_AUTHENTICATION=false) or, when using the Helm chart, configure global.jwtOnly: true.

Who should check

Teams running Eclipse Ditto 1.1.0 through 3.9.8 with gateway pre-authentication enabled, including default Helm chart installs with global.jwtOnly=false.

Not fixed by: A reverse proxy that only overwrites the header does not stop this.

“Impacted are Eclipse Ditto deployments where pre-authentication is enabled”

github.com

What to do

  1. Check every install: default setups are affected.

  2. Upgrade to a fixed version: 3.9.9, 3.8.15.

  3. Workaround: Set ENABLE_PRE_AUTHENTICATION=false in the gateway, or set global.jwtOnly: true when using the Helm chart.

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-120753 (Eclipse Ditto gateway accepts `x-ditto-pre-authenticated` from a URL query parameter, allowing unauthenticated subject impersonation…), 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-120753 (entry last updated 2026-11-19):
Affected:
- Eclipse Foundation Eclipse Ditto: from 1.1.0, through 3.9.8
Fixed versions: 3.9.9, 3.8.15.
Conditions (all must be true for the bug to be hit):
- Eclipse Ditto versions 1.1.0 to 3.9.8 are affected (source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/539)
- Gateway pre-authentication is enabled (source: https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1346)
- Helm chart installed with default global.jwtOnly=false, using the bundled nginx (source: https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1346)
- Attacker must reach the chart nginx /api route and know or guess a policy subject and Thing ID (source: https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1346)
- Target policy must grant the chosen subject the requested operation (source: https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1346)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
Workaround: Set ENABLE_PRE_AUTHENTICATION=false in the gateway, or set global.jwtOnly: true when using the Helm chart. (source: https://github.com/eclipse-ditto/ditto/security/advisories/GHSA-chwq-wg27-qvfr)
CISA KEV: CVE-2026-120753 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-120753 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/1346
- https://github.com/eclipse-ditto/ditto/security/advisories/GHSA-chwq-wg27-qvfr
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/539
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-120753
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-120753"}.

Affected versions

cve.now Index

47Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure22/25Default setups, reachable over the network without a login
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.1, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 72 if added to CISA KEV
  • Would score about 67 if CISA's SSVC rates exploitation active

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: total

  5. Record last updated

Evidence 5

Questions about CVE-2026-120753

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

The gateway accepts the x-ditto-pre-authenticated value from a URL query parameter, so a request without valid credentials can act as a chosen policy subject. That lets it read and modify all Things and Policies that subject is granted access to.

Source: gitlab.eclipse.org, gitlab.eclipse.org, github.com

Which versions are affected by CVE-2026-120753?

Eclipse Ditto: from 1.1.0 through 3.9.8.

Source: cve.now feed data

Am I affected, and how do I check?

Eclipse Ditto versions 1.1.0 through 3.9.8 are affected when gateway pre-authentication is enabled, which the rendered gateway Deployment shows as ENABLE_PRE_AUTHENTICATION=true. The reported Helm setup is the default global.jwtOnly=false with the bundled nginx, so check the gateway environment variable and the global.jwtOnly value in the chart.

Source: gitlab.eclipse.org, gitlab.eclipse.org, github.com

How do I fix CVE-2026-120753?

Upgrade to Eclipse Ditto 3.9.9 or 3.8.15, which are the fixed versions. Until the upgrade is applied, the workarounds are setting ENABLE_PRE_AUTHENTICATION=false in the gateway or setting global.jwtOnly: true in the Helm chart.

Source: gitlab.eclipse.org, gitlab.eclipse.org, github.com

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