# CVE-2026-14902: Open redirect in Xtraction

> Remote unauthenticated attackers can redirect users to arbitrary external URLs in Ivanti Xtraction, potentially facilitating phishing attacks.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-8qwq-c4m2-h4xh

## What is CVE-2026-14902?

CVE-2026-14902 is a medium-severity vulnerability in ivanti Xtraction, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An open redirect in Ivanti Xtraction before version 2026.2.1 allows a remote unauthenticated attacker to redirect users to arbitrary external URLs.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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

It affects 1 product.


Products: Ivanti Xtraction.

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

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

## Is CVE-2026-14902 being exploited?

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

## Other vulnerabilities in ivanti Xtraction

- [CVE-2026-8043](https://insights.sbomify.com/CVE-2026-8043/): Path traversal in Xtraction (critical 9.6)
- [CVE-2026-14903](https://insights.sbomify.com/CVE-2026-14903/): Path traversal in Xtraction (high 7.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14902 is a medium-severity vulnerability in ivanti Xtraction, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14902 in the wild and no public exploit code.

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

## Sources

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

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