CVE-2026-120753
Eclipse Ditto gateway accepts `x-ditto-pre-authenticated` from a URL query parameter, allowing unauthenticated subject impersonation (default Helm chart)
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`.
INFO
Published Date :
Nov. 19, 2026, 2:48 p.m.
Last Modified :
Nov. 19, 2026, 2:48 p.m.
Remotely Exploit :
Yes !
Source :
eclipse
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 4.0 | CRITICAL | e51fbebd-6053-4e49-959f-1b94eeb69a2c |
Solution
- Disable pre-authentication in the gateway settings.
- Configure Helm chart with 'global.jwtOnly: true'.
- Ensure only trusted sources provide authentication.
- Validate JWT before allowing pre-authentication.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-120753 vulnerability anywhere in the article.