Eclipse Foundation · Eclipse Ditto · CWE-290 · CWE-287 · published 2026-11-19
CVE-2026-120753Eclipse Ditto gateway accepts `x-ditto-pre-authenticated` from a URL query parameter, allowing unauthenticated subject impersonation (default Helm chart)
This month Public proof-of-concept exists (SSVC exploitation: poc).
CVE-2026-120753 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 0.8% chance of exploitation in the next 30 days, higher than 56% of all CVEs. This Eclipse Ditto vulnerability: CVSS 9.1 (v4.0), a successful attack gives total control of the component. Patch in your normal monthly cycle.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
No fixed version is recorded here yet. Check the vendor advisory linked from the CVE record below.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.8% (57th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 9.1 (v4.0)CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N | CNA / CISA ADP |
| SSVC exploitation | poc | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Weakness: CWE-290: Authentication Bypass by Spoofing · CWE-287: Improper Authentication
Affected versions (from the CVE record)#
- Eclipse Foundation Eclipse Ditto
1.1.0through3.9.8(affected)
Description (from the CVE record)#
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`.
Quoted from the CVE Program record.