# CVE-2026-107503: Open redirect in Ditto Explorer UI

> Attackers can steal user tokens by tricking victims into visiting a crafted link that redirects authentication to a malicious server.

- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-8767-g5qv-9jcf, GHSA-g8w6-jp67-cwcc

## What is CVE-2026-107503?

CVE-2026-107503 is a high-severity vulnerability in Eclipse Ditto Ditto Explorer UI, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-346 (Origin Validation Error), CWE-522 (Insufficiently Protected Credentials), CWE-15 (External Control of System or Configuration Setting)

## Which versions are affected by CVE-2026-107503?


## How do I fix CVE-2026-107503?

No fix has been published for CVE-2026-107503 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-107503 being exploited?

There is no known exploitation of CVE-2026-107503 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107503 and fix it if it is affected.

What it is: CVE-2026-107503 is a high-severity vulnerability in Eclipse Ditto Ditto Explorer UI, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-107503 in the wild and no public exploit code.

Affected product: Eclipse Ditto Ditto Explorer UI. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-107503/ (Markdown: https://insights.sbomify.com/CVE-2026-107503/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107503
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107503
- OSV: https://osv.dev/vulnerability/CVE-2026-107503

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-107503/
Summaries are generated and may contain mistakes; the official description above is the record.