CVE-2026-14902
Awaiting Analysis Awaiting Analysis - Queue

Open Redirect Vulnerability in Ivanti Xtraction

Vulnerability report for CVE-2026-14902, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-14

Last updated on: 2026-07-14

Assigner: ivanti

Description

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

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-14
Last Modified
2026-07-14
Generated
2026-08-03
AI Q&A
2026-07-14
EPSS Evaluated
2026-08-02
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
ivanti xtraction to 2026.2.1 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-601 The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is an open redirect issue in Ivanti Xtraction versions before 2026.2.1. An open redirect occurs when an application allows user-supplied input to control the destination of a redirect without proper validation. In this case, a remote unauthenticated attacker can craft a malicious link that, when clicked by a user, redirects them to an arbitrary external URL of the attacker's choice.

The CVSS v3.1 score for this vulnerability is 4.0, with a vector of AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N. This means the vulnerability is network-exploitable, requires high attack complexity, and does not require privileges or user interaction. The impact is low integrity, meaning the attacker can manipulate the redirect destination, but there is no confidentiality or availability impact.

Detection Guidance

Detecting an open redirect vulnerability in Ivanti Xtraction before version 2026.2.1 requires checking for unexpected or unauthorized URL redirections. Since this is an open redirect issue, you can test for it by analyzing network traffic or manually inspecting the application's behavior.

  • Use a web proxy tool like Burp Suite or OWASP ZAP to intercept and inspect HTTP requests and responses. Look for parameters in URLs that may contain redirect destinations (e.g., 'url=', 'redirect=', 'next=').
  • Manually test the application by appending common open redirect parameters to URLs and observing if the application redirects to an external domain. For example, try accessing a URL like 'https://your-xtraction-instance.com/login?redirect=https://evil.com' and check if the application redirects to 'evil.com'.
  • Check the version of Ivanti Xtraction running in your environment. If it is before 2026.2.1, it is likely vulnerable. You can verify the version through the application's admin interface or by checking installed software on the server.

There are no specific commands provided for detection, as this is primarily a web application vulnerability that requires manual testing or the use of security tools.

Impact Analysis

The impact of this vulnerability depends on how you or your organization use Ivanti Xtraction. Here are potential risks:

  • Phishing attacks: Attackers can exploit the open redirect to send legitimate-looking links that redirect users to malicious websites. This can trick users into entering sensitive information like credentials or financial details.
  • Malware distribution: The attacker could redirect users to websites hosting malware, leading to potential infections or further compromise of systems.
  • Reputation damage: If your organization's users are redirected to malicious or inappropriate sites, it could harm your organization's reputation.
  • Bypass of security controls: Open redirects can be used to bypass security measures that rely on domain whitelisting or other URL-based restrictions.
Compliance Impact

This vulnerability could have implications for compliance with various standards and regulations, depending on the context of its use:

  • GDPR (General Data Protection Regulation): If the open redirect is exploited to trick users into disclosing personal data (e.g., through phishing), it could lead to a data breach. Under GDPR, organizations must implement appropriate security measures to protect personal data. Failure to patch this vulnerability or mitigate its risks could be seen as a violation of these requirements.
  • HIPAA (Health Insurance Portability and Accountability Act): If Ivanti Xtraction is used in a healthcare environment to handle protected health information (PHI), an open redirect could be exploited to redirect users to malicious sites, potentially leading to unauthorized access to PHI. This could violate HIPAA's Security Rule, which requires safeguards to protect PHI.
  • PCI DSS (Payment Card Industry Data Security Standard): If the application is involved in processing payment card data, an open redirect could be used as part of an attack chain to steal cardholder data. PCI DSS requires organizations to protect systems against vulnerabilities that could lead to data breaches.

While the vulnerability itself does not directly violate these regulations, its exploitation could lead to non-compliance if it results in a data breach or failure to meet security requirements. Organizations should assess the risk and apply patches or mitigations to maintain compliance.

Mitigation Strategies

To mitigate the open redirect vulnerability in Ivanti Xtraction before version 2026.2.1, follow these immediate steps:

  • Upgrade to Ivanti Xtraction version 2026.2.1 or later, as this version contains the fix for the vulnerability. Check Ivanti's official release notes or security advisories for the latest version.
  • If upgrading is not immediately possible, apply any available patches or workarounds provided by Ivanti. Monitor Ivanti's security advisories for updates.
  • Restrict access to the Ivanti Xtraction application to trusted networks or users only. Use firewalls or network segmentation to limit exposure.
  • Implement input validation and sanitization for URL parameters to prevent malicious redirects. Ensure that any redirect parameters only allow whitelisted domains or relative paths.
  • Monitor network traffic and application logs for suspicious redirect attempts or unusual external domain requests.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-14902. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart