# CVE-2026-42195: Unvalidated gitlab URL parameter redirects OAuth authorize step to attacker-controlled host

> Attackers can redirect OAuth authorization to malicious hosts via a URL parameter, enabling credential phishing and token theft in draw.io.

- **Severity:** Low 3.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A: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 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-8x7j-m8px-7p8x

## What is CVE-2026-42195?

CVE-2026-42195 is a low-severity vulnerability in jgraph drawio, published on 8 May 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

draw.io is a configurable diagramming and whiteboarding application. Prior to version 29.7.9, the draw.io client accepts a ?gitlab= URL parameter that overrides the GitLab server URL used during OAuth sign-in. A crafted link causes the user's click on draw.io's "Authorize in GitLab" dialog to open a popup on the attacker-controlled host instead of gitlab.com. This can lead to credential fishing and session state token exfiltration. This issue has been patched in version 29.7.9.

Weakness: CWE-601 (URL Redirection to Untrusted Site), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-42195 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42195 is a low-severity vulnerability in jgraph drawio, published on 8 May 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-42195 in the wild and no public exploit code.

Affected product: jgraph drawio. 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-42195/ (Markdown: https://insights.sbomify.com/CVE-2026-42195/index.md)
```

## Sources

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

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