# CVE-2025-50055: Cross-site scripting in Access Server

> Remote SAML ACS servers can inject arbitrary scripts via RelayState in OpenVPN Access Server, potentially compromising user sessions.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Oct 2025
- **Updated:** 30 Oct 2025
- **Also known as:** GHSA-pcpf-m9xc-438x

## What is CVE-2025-50055?

CVE-2025-50055 is a medium-severity cross-site scripting vulnerability in OpenVPN Access Server, published on 27 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cross-site scripting (XSS) vulnerability in the SAML Authentication module in OpenVPN Access Server version 2.14.0 through 2.14.3 allows configured remote SAML Assertion Consumer Service (ACS) endpoint servers to inject arbitrary web script or HTML via the RelayState parameter

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-50055?


## How do I fix CVE-2025-50055?

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

## Is CVE-2025-50055 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-50055 and fix it if it is affected.

What it is: CVE-2025-50055 is a medium-severity cross-site scripting vulnerability in OpenVPN Access Server, published on 27 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-50055 in the wild and no public exploit code.

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

## Sources

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

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