# What is CVE-2020-26217? > CVE-2020-26217 is a high-severity flaw (CVSS 8.8) in Xstream, published on 16 November 2020. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 85%. If you run an affected version, plan in the vendor’s fix. Canonical page: https://www.precursorintelligence.com/what-is/cve-2020-26217 ## At a glance - **Verdict:** Fix this soon. Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month. - **Precursor Intelligence risk score:** 72 out of 100 (High); action: Patch now. Kept up to date as the evidence changes. - **Severity:** High (CVSS 8.8 out of 10) - **Known to be exploited:** No, not on the list of flaws known to be exploited today - **Chance of use in the next 30 days:** 85% (latest exploit-likelihood forecast) - **Published:** 16 November 2020 - **Record last updated:** 23 May 2025 - **Main product:** Xstream - **Affected products:** 15 ## What is CVE-2020-26217? In plain terms It can be attacked from anywhere on the internet with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline. ### The official description XStream before version 1.4.14 is vulnerable to Remote Code Execution.The vulnerability may allow a remote attacker to run arbitrary shell commands only by manipulating the processed input stream. Only users who rely on blocklists are affected. Anyone using XStream's Security Framework allowlist is not affected. The linked advisory provides code workarounds for users who cannot upgrade. The issue is fixed in version 1.4.14. ### What kind of flaw is it? - CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') ### How an attack on it works - Where an attacker can be: Anywhere on the internet - How hard it is to pull off: Easy: no special conditions - Login needed first: An ordinary user account - Does someone have to click: No, nobody has to do anything - What an attacker gets: Can read data, change data and take it offline Severity vector: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` ## Is CVE-2020-26217 being exploited? Not that we know of It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 85%. That can change at any time, which is why we keep watching. Exploit likelihood over the last 7 days: 85%, 85%, 85%, 85%, 85%, 85%, 85%. ### Timeline - 16 November 2020: Published - 23 May 2025: Record last updated ### How Precursor Intelligence ranks it CVE-2020-26217 scores **72 out of 100 (High)**, with the action "Patch now". Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less: - Evidence it is being exploited: biggest factor - How severe it is: strong factor - How widely exposed it is: smaller factor - Threat activity around it: smaller factor 85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it. ## Who is affected by CVE-2020-26217? The published record lists 15 products. Versions are as published: "before 1.4.14" means every version up to, but not including, 1.4.14. - [Xstream](https://www.precursorintelligence.com/product/xstream/xstream) by [Xstream](https://www.precursorintelligence.com/vendors/xstream) (Application): before 1.4.14 - [Retail Xstore Point of Service](https://www.precursorintelligence.com/product/oracle/retail_xstore_point_of_service) by [Oracle](https://www.precursorintelligence.com/vendors/oracle) (Application): 16.0.6, 17.0.4, 18.0.3, 19.0.2 - [Banking Cash Management](https://www.precursorintelligence.com/product/oracle/banking_cash_management) by [Oracle](https://www.precursorintelligence.com/vendors/oracle) (Application): 14.2, 14.3, 14.5 - [Banking Corporate Lending Process Management](https://www.precursorintelligence.com/product/oracle/banking_corporate_lending_process_management) by [Oracle](https://www.precursorintelligence.com/vendors/oracle) (Application): 14.2, 14.3, 14.5 - [Banking Credit Facilities Process Management](https://www.precursorintelligence.com/product/oracle/banking_credit_facilities_process_management) by [Oracle](https://www.precursorintelligence.com/vendors/oracle) (Application): 14.2, 14.3, 14.5 - [Banking Platform](https://www.precursorintelligence.com/product/oracle/banking_platform) by [Oracle](https://www.precursorintelligence.com/vendors/oracle) (Application): 2.4.0, 2.7.1, 2.9.0 - [Banking Supply Chain Finance](https://www.precursorintelligence.com/product/oracle/banking_supply_chain_finance) by [Oracle](https://www.precursorintelligence.com/vendors/oracle) (Application): 14.2, 14.3, 14.5 - [Banking Trade Finance Process Management](https://www.precursorintelligence.com/product/oracle/banking_trade_finance_process_management) by [Oracle](https://www.precursorintelligence.com/vendors/oracle) (Application): 14.2, 14.3, 14.5 - [Banking Virtual Account Management](https://www.precursorintelligence.com/product/oracle/banking_virtual_account_management) by [Oracle](https://www.precursorintelligence.com/vendors/oracle) (Application): 14.2.0, 14.3.0, 14.5.0 - [Business Activity Monitoring](https://www.precursorintelligence.com/product/oracle/business_activity_monitoring) by [Oracle](https://www.precursorintelligence.com/vendors/oracle) (Application): 11.1.1.9.0, 12.2.1.3.0, 12.2.1.4.0 - [Activemq](https://www.precursorintelligence.com/product/apache/activemq) by [Apache](https://www.precursorintelligence.com/vendors/apache) (Application): before 5.15.14, 5.16.0 - [Debian Linux](https://www.precursorintelligence.com/product/debian/debian_linux) by [Debian](https://www.precursorintelligence.com/vendors/debian) (Operating system): 9.0, 10.0 - [Communications Policy Management](https://www.precursorintelligence.com/product/oracle/communications_policy_management) by [Oracle](https://www.precursorintelligence.com/vendors/oracle) (Application): 12.5.0 - [Endeca Information Discovery Studio](https://www.precursorintelligence.com/product/oracle/endeca_information_discovery_studio) by [Oracle](https://www.precursorintelligence.com/vendors/oracle) (Application): 3.2.0.0 - [Snapmanager](https://www.precursorintelligence.com/product/netapp/snapmanager) by [Netapp](https://www.precursorintelligence.com/vendors/netapp) (Application): all versions ## How do I fix CVE-2020-26217? 1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list. 2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list. 3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in. 4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood. ### References - [github.com](https://github.com/x-stream/xstream/commit/0fec095d534126931c99fd38e9c6d41f5c685c1a) (Patch, Third-party advisory) - [oracle.com](https://www.oracle.com//security-alerts/cpujul2021.html) (Patch, Third-party advisory) - [oracle.com](https://www.oracle.com/security-alerts/cpuApr2021.html) (Patch, Third-party advisory) - [oracle.com](https://www.oracle.com/security-alerts/cpuoct2021.html) (Patch, Third-party advisory) - [x-stream.github.io](https://x-stream.github.io/CVE-2020-26217.html) (Exploit, Mitigation, Vendor advisory) - [github.com](https://github.com/x-stream/xstream/security/advisories/GHSA-mw36-7c6c-q4q2) (Mitigation, Third-party advisory) - [lists.apache.org](https://lists.apache.org/thread.html/r2de526726e7f4db4a7cb91b7355070779f51a84fd985c6529c2f4e9e%40%3Cissues.activemq.apache.org%3E) (Issue tracking, Mailing list) - [lists.apache.org](https://lists.apache.org/thread.html/r7c9fc255edc0b9cd9567093d131f6d33fde4c662aaf912460ef630e9%40%3Ccommits.camel.apache.org%3E) (Issue tracking, Mailing list) - [lists.apache.org](https://lists.apache.org/thread.html/r826a006fda71cc96fc87b6eca4b5d195f19a292ad36cea501682c38c%40%3Cissues.activemq.apache.org%3E) (Issue tracking, Mailing list) - [lists.apache.org](https://lists.apache.org/thread.html/redde3609b89b2a4ff18b536a06ef9a77deb93d47fda8ed28086fa8c3%40%3Cissues.activemq.apache.org%3E) (Issue tracking, Mailing list) - [lists.debian.org](https://lists.debian.org/debian-lts-announce/2020/12/msg00001.html) (Mailing list, Third-party advisory) - [security.netapp.com](https://security.netapp.com/advisory/ntap-20210409-0004/) (Third-party advisory) - [debian.org](https://www.debian.org/security/2020/dsa-4811) (Third-party advisory) - [oracle.com](https://www.oracle.com/security-alerts/cpuapr2022.html) (Not applicable, Third-party advisory) - [oracle.com](https://www.oracle.com/security-alerts/cpujan2022.html) (Not applicable, Third-party advisory) ## Questions ### What is CVE-2020-26217? CVE-2020-26217 is a high-severity flaw in Xstream, published on 16 November 2020. It can be attacked from anywhere on the internet with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline. ### How serious is CVE-2020-26217? It scores 8.8 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2020-26217 is 72 out of 100, which is High. Its action is "Patch now". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month. ### Is CVE-2020-26217 being exploited? It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 85%. That can change at any time, which is why we keep watching. ### Which versions does CVE-2020-26217 affect? For Xstream: before 1.4.14. The record lists 15 products in all, each with its versions, under "Who is affected" on this page. ### How do I fix CVE-2020-26217? Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. ## Does CVE-2020-26217 affect you? Precursor Intelligence keeps checking for you: - **Tell us what you run.** Pick your software from a list, or let us work it out from your website. - **We match it to every flaw.** Over 400,000 published flaws, checked against your list. - **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it. - **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools. Start free (no card, nothing to install): https://www.precursorintelligence.com/register Book a demo: https://www.precursorintelligence.com/contact