Skip to main content
VulnerabilityPublished

CVE-2026-120753: Eclipse Ditto · Authentication Bypass by Spoofing

Affects Eclipse DittoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical.

Data as of 19 Nov 2026, 15:06 UTC

CVSS 4.0 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (eclipse)CVSS 4.09.1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Eclipse FoundationEclipse DittoAffected
  • >=1.1.0 <=3.9.8
Fixed in–

AI-suggested

Disable pre-authentication in the gateway by setting `ENABLE_PRE_AUTHENTICATION=false`. Alternatively, when deploying with the Helm chart, configure `global.jwtOnly: true` to enforce JWT-only authentication and prevent the acceptance of the pre-authenticated subject from the query parameter. These mitigations prevent attackers from spoofing authentication and protect the system from unauthorized access.

Description

Eclipse Ditto versions 1.1.0 through 3.9.8 contain an authentication bypass vulnerability when pre-authentication is enabled. The gateway service improperly accepts a pre-authenticated subject from an undocumented URL query parameter, allowing unauthenticated attackers to impersonate any policy subject. This occurs because the gateway trusts the query parameter in addition to the HTTP header, and the default Helm chart configuration enables this insecure behavior. Attackers can read and modify Things and Policies with the permissions of the spoofed subject.

References

Community reviews

Loading reviews…