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.
{
"cna_assigner": "eclipse",
"cwe_ids": [
"CWE-287",
"CWE-290"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/120xxx/CVE-2026-120753.json"
}