CVE-2026-14903
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPath traversal in Ivanti Xtraction before version 2026.2.1 allows a remote authenticated attacker to read arbitrary files outside the web root.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA path traversal vulnerability in Ivanti Xtraction versions prior to 2026.2.1 allows a remote authenticated attacker to read arbitrary files outside the web root directory. The vulnerability stems from insufficient input validation in file handling mechanisms, enabling directory traversal sequences (such as '../') to access sensitive system files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2026.2.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Ivanti Xtraction installation and versionLocate the Ivanti Xtraction installation directory or check the web application banner/version information accessible through the product's admin or login interface. Common locations include /opt/xtraction or C:\Program Files\Ivanti\Xtraction on the server, or check the application's 'About' or 'System Information' page if accessible.Affected if The installed version is identified as anything prior to 2026.2.1
-
Verify the Xtraction web service is accessibleConfirm that the Xtraction web interface is reachable via HTTP/HTTPS. This is typically accessible on port 8080 or 8443, or through the organization's configured web server port. Attempt to access the login page or API endpoints.Affected if The web service is exposed and accessible to network users
-
Check if file download or file handling features are enabledReview the Xtraction configuration settings or feature flags to determine if file download, file retrieval, or document handling modules are active. This may be visible in the admin console under system settings or through configuration XML/YAML files in the installation directory.Affected if File handling or download functionality is enabled in the configuration
-
Inspect web server logs for directory traversal attemptsExamine the Xtraction web server logs (typically found in logs/ or tomcat/logs/ within the installation directory) for patterns containing '../', '..\', or unusual file path requests that may indicate exploitation attempts.Affected if Log entries show directory traversal sequences targeting system files outside the web root
A user is affected if Ivanti Xtraction is running with a version lower than 2026.2.1 and the web-based file handling functionality is accessible and enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2026.2.1
Upgrade Ivanti Xtraction to version 2026.2.1 or later to obtain the patched code that properly sanitizes file path inputs. Alternatively, implement web application firewall (WAF) rules to block directory traversal patterns as an interim control.
2026.2.1
- Upgrade Ivanti Xtraction to version 2026.2.1 or later
- Verify the upgrade was successful by checking the version number in the product UI or about page
- Confirm the path traversal vulnerability is resolved by testing that file access is now properly restricted to the web root
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14903 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-14903 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data