External risk intelligence

Eclipse Ditto Pre-Authentication Bypass Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-120753

Eclipse Ditto is a digital twin middleware often deployed as a gateway service or API endpoint to manage Things and Policies. Because it functions as a service interface and is frequently deployed using Helm charts in environments where it acts as a central hub for device data, it is commonly exposed as an internet-facing or network-facing API service.

Authentication Bypass

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in Eclipse Ditto, specifically when pre-authentication is enabled, allows unauthenticated remote attackers to bypass security checks and impersonate any user. This is possible by sending a crafted request with an invalid Bearer token and a specific query parameter, enabling them to read or modify sensitive data without proper authorization.

  • Attackers can impersonate any user.
  • Protects critical digital twin data and configurations.
  • Confirm relevance and exposure for Ditto gateways.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker can exploit a flaw in Eclipse Ditto's gateway service to impersonate any user. By sending a crafted request with a specific URL query parameter alongside an invalid Bearer token, an attacker can bypass authentication checks. This allows them to access and modify digital twin data and policies as if they were the legitimate user.

  • No authentication required to start.
  • Invalid Bearer token and query parameter trigger.
  • Read and modify data with subject permissions.

Live Threat

Current exploitation, exposure, and threat context

When pre-authentication is enabled, an unauthenticated remote attacker could impersonate any chosen policy subject by leveraging an undocumented URL query parameter. This could allow them to read and modify digital twins and their associated policies.

  • Digital twins and policies at risk.
  • Attacker bypasses authentication via query parameter.
  • Unauthorized access to twin data and configuration.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application owners and platform teams are most likely responsible for addressing this vulnerability in Eclipse Ditto. The initial focus should be on inventorying deployed instances, assessing their exposure and criticality, and then coordinating remediation with the relevant teams.

  • Application owners and platform teams.
  • Verify pre-authentication configurations and network exposure.
  • Plan staged remediation based on risk assessment.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Eclipse Ditto?

Eclipse Ditto is an open-source middleware framework used to create and manage digital twins. It acts as a central hub that bridges the gap between physical devices and digital applications, allowing users to interact with device data, state, and permissions through standardized APIs and a flexible policy-based security model.

What does CVE-2026-120753 mean for security?

This vulnerability involves Improper Authentication (CWE-287) and Authentication Bypass by Spoofing (CWE-290). In affected versions, the system incorrectly trusts identity information provided in a URL query parameter, which can be manipulated. This allows an attacker to masquerade as another user or service, gaining unauthorized access to manage digital twins and policies.

How can an attacker trigger this vulnerability?

An attacker triggers this by sending a request to the Ditto gateway containing an undocumented URL query parameter that specifies a chosen subject. The bug does not require a valid login; it only works when pre-authentication is enabled. Requests that do not include the malicious query parameter or that are sent to systems where pre-authentication is disabled are not affected.

Who should be concerned about this flaw?

Teams managing Eclipse Ditto deployments should evaluate their risk. According to Halo Surface Signal, because Ditto often acts as an internet-facing or network-facing API gateway for device data, instances reachable from untrusted networks are at the highest risk of unauthorized access. Internal instances with restricted access are also susceptible if an attacker gains entry to the local network.

What are the first steps to secure my deployment?

Verify your gateway configuration immediately. If you are using the Ditto Helm chart, update your settings to set 'global.jwtOnly' to true. If you are using pre-authentication, set the 'ENABLE_PRE_AUTHENTICATION' environment variable to false to disable this feature. Prioritize these changes for any instance that handles sensitive digital twin data.

References