CVE-2026-107503

OAuth Authorization Code Theft via Unvalidated OIDC Authority in Eclipse Ditto Explorer

Published Oct 8, 2026 CVSS 4.0 · 7.1 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

An attacker can craft a link that injects an attacker‑controlled OIDC authority into the Eclipse Ditto Explorer UI. When autoSso is enabled the UI automatically initiates a login with a legitimate identity provider, but the returned authorization code is then exchanged, along with the PKCE code_verifier, at the attacker’s token endpoint. This allows the attacker to redeem the code for bearer, access and refresh tokens belonging to the victim, thereby enabling account takeover. Additionally, an attacker‑controlled api_uri can cause the UI to send the victim’s bearer token or Basic credentials directly to the attacker, providing another avenue for credential theft.

Affected Systems

Eclipse Ditto Ditto Explorer UI versions 3.6.0 through 3.9.7 are affected. The vulnerability arises from an unvalidated environment URL configuration that is persisted across sessions, allowing repeated token theft without a new crafted link.

Risk and Exploitability

The CVSS score of 7.1 indicates high severity. EPSS data is not available, although the lack of a KEV listing suggests no publicly known exploit has been reported yet. The likely attack vector is remote, relying on a user clicking a malicious link that activates autoSso. Given the persistence of the configuration, continued exposure is possible if the UI is reused without intervention.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Eclipse Ditto Ditto Explorer UI to a version that includes proper validation of the OIDC authority and token endpoint settings.
  • If an immediate update is not possible, disable the autoSso feature in the Ditto Explorer UI configuration to stop automatic login flows until the vulnerability is addressed.
  • Configure the api_uri setting to only accept trusted domain names, preventing the UI from sending credentials to attacker‑controlled endpoints.

Generated by OpenCVE AI on October 8, 2026 at 10:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description Unvalidated environments URL allows OAuth authorization code + PKCE verifier theft and account takeover via injected OIDC authority in Ditto Explorer in Eclipse Ditto Ditto Explorer [3.6.0,3.9.7] allows a craft link 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 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.
References
Type Values Removed Values Added
First Time appeared Eclipse Ditto
Eclipse Ditto ditto Explorer Ui
Vendors & Products Eclipse Ditto
Eclipse Ditto ditto Explorer Ui
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Title OAuth Authorization Code Theft via Unvalidated OIDC Authority in Eclipse Ditto Explorer
Type Values Removed Values Added
Description Unvalidated environments URL allows OAuth authorization code + PKCE verifier theft and account takeover via injected OIDC authority in Ditto Explorer in Eclipse Ditto Ditto Explorer [3.6.0,3.9.7] allows a craft link 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.
Weaknesses CWE-15
CWE-346
CWE-522
References
Metrics cvssV4_0

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:L/VA:N/SC:H/SI:H/SA:N'}

Weaknesses
  • CWE-15

    External Control of System or Configuration Setting

  • CWE-346

    Origin Validation Error

  • CWE-522

    Insufficiently Protected Credentials

Sources

Status
PUBLISHED
Assigner
eclipse
Published
Updated
Oct 15, 2026, 1:09 PM
Reserved
Oct 8, 2026, 9:09 AM
Status
Awaiting Analysis
Published
Oct 8, 2026, 10:17 AM
Modified
Oct 15, 2026, 2:17 PM