In Eclipse Ditto versions 3.6.0 to 3.8.13 and 3.9.0 to 3.9.7, the Ditto Explorer UI loads its complete environment configuration, including the Ditto API URI and the OpenID Connect (OIDC) provider settings, from an arbitrary
cross-origin URL supplied in the environmentsURL query parameter. It adopts this configuration without user confirmation and persists it in the browser's localStorage. A crafted link can therefore set an attacker-controlled OIDC
authority with autoSso enabled. The UI then automatically starts a login at the genuine identity provider but exchanges the returned authorization code together with its PKCE code_verifier at an attacker-controlled token
endpoint. This lets the attacker redeem the code for the victim's access and refresh tokens. Alternatively, an attacker-controlled api_uri causes the UI to send the victim's bearer token or Basic credentials to the attacker. Because
the configuration is persisted, later visits to the UI without the crafted link repeat the token theft. In versions 3.9.0 to 3.9.7, the Swagger UI OIDC integration of the Helm chart and the Docker Compose deployment is affected in
the same way, but requires the user to start the login. The issue is fixed in 3.8.14 and 3.9.8.
0.2%(unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-15External Control of System or Configuration Setting CWE-346Origin Validation Error CWE-522Insufficiently Protected Credentials
Show the promptExplain CVE-2026-107503 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107503?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107503?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-107503 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
eclipse ditto:ditto explorer ui
Versions
From the CNA's record in the CVE List.
Product
Affected
Eclipse Ditto Ditto Explorer UI
from 3.6.0 before 3.8.14
Eclipse Ditto Ditto Explorer UI
from 3.9.0 before 3.9.8
Attack patterns (CAPEC)
CAPEC-13 Subverting Environment Variable Values Likelihood: High · Severity: Very High
CAPEC-69 Target Programs with Elevated Privileges Likelihood: High · Severity: Very High
CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
CAPEC-146 XML Schema Poisoning Likelihood: Low · Severity: High
CAPEC-176 Configuration/Environment Manipulation Severity: Medium
CAPEC-203 Manipulate Registry Information Severity: Medium
CAPEC-270 Modification of Registry Run Keys Likelihood: Medium · Severity: Medium
CAPEC-271 Schema Poisoning Likelihood: Low · Severity: High