# CVE-2025-25234: Security feature bypass in Omnissa Unified Access Gateway (UAG)

> Attackers can bypass CORS restrictions to access sensitive networks via the Unified Access Gateway.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/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:** 17 Apr 2025
- **Updated:** 17 Apr 2025
- **Also known as:** GHSA-7hqv-m3mr-cv2v

## What is CVE-2025-25234?

CVE-2025-25234 is a high-severity vulnerability in Omnissa Unified Access Gateway (UAG), published on 17 Apr 2025. 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

Omnissa UAG contains a Cross-Origin Resource Sharing (CORS) bypass vulnerability. A malicious actor with network access to UAG may be able to bypass administrator-configured CORS restrictions to gain access to sensitive networks.

Weakness: CWE-942 (Permissive Cross-domain Security Policy with Untrusted Domains)

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

It affects 1 product.


Products: Omnissa Unified Access Gateway.

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

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

## Is CVE-2025-25234 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25234 is a high-severity vulnerability in Omnissa Unified Access Gateway (UAG), published on 17 Apr 2025. 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-2025-25234 in the wild and no public exploit code.

Affected product: Omnissa Unified Access Gateway (UAG). 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-25234/ (Markdown: https://insights.sbomify.com/CVE-2025-25234/index.md)
```

## Sources

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

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