CVE-2026-120753
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
CVSS
—
Sem CVSS
EPSS
—
KEV
—
Exploit Today
—
0-100
Publicado: 19 de nov. de 2026 · Última mod.: 19 de nov. de 2026 · CWE-287 · CWE-290
Ainda não há histórico EPSS suficiente.
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`.
- github.comhttps://github.com/eclipse-ditto/ditto/security/advisories/GHSA-chwq-wg27-qvfr
- gitlab.eclipse.orghttps://gitlab.eclipse.org/security/cve-assignment/-/work_items/539
- gitlab.eclipse.orghttps://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1346
- gitlab.eclipse.orghttps://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1346