# CVE-2026-63650: Auth bypass in OpenVPN

> Remote authenticated users can be misidentified by ignoring the configured X.509 username identity lookup field in OpenVPN.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:A/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-63650, GHSA-f94x-h63g-g9m8

## What is CVE-2026-63650?

CVE-2026-63650 is a low-severity authentication bypass vulnerability in OpenVPN, published on 14 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

OpenVPN 2.7_alpha1 through 2.7.5 using mbedTLS allows remote authenticated users to be misidentified by ignoring the configured X.509 username identity lookup field

Weakness: CWE-295 (Improper Certificate Validation), CWE-115 (Misinterpretation of Input)

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


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

Upgrade to a fixed version.

## Is CVE-2026-63650 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-63650 is a low-severity authentication bypass vulnerability in OpenVPN, published on 14 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-63650 in the wild and no public exploit code.

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

## Sources

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

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