High

XStream can be used for Remote Code Execution

  • Disclosed: 16.11.2020
  • Updated: 11.10.2026 12:22

Impact

The vulnerability may allow a remote attacker to run arbitrary shell commands only by manipulating the processed input stream.

Patches

If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.14.

Workarounds

No user is affected, who followed the recommendation to setup XStream's Security Framework with a whitelist! Anyone relying on XStream's default blacklist can immediately switch to a whilelist for the allowed types to avoid the vulnerability.

Users of XStream 1.4.13 or below who still want to use XStream default blacklist can use a workaround depending on their version in use.

Users of XStream 1.4.13 can simply add two lines to XStream's setup code:

java
xstream.denyTypes(new String[]{ "javax.imageio.ImageIO$ContainsFilter" });
xstream.denyTypes(new Class[]{ java.lang.ProcessBuilder.class });

Users of XStream 1.4.12 to 1.4.7 who want to use XStream with a black list will have to setup such a list from scratch and deny at least the following types: javax.imageio.ImageIO$ContainsFilter, java.beans.EventHandler, java.lang.ProcessBuilder, java.lang.Void and void.

java
xstream.denyTypes(new String[]{ "javax.imageio.ImageIO$ContainsFilter" });
xstream.denyTypes(new Class[]{ java.lang.ProcessBuilder.class, java.beans.EventHandler.class, java.lang.ProcessBuilder.class, java.lang.Void.class, void.class });

Users of XStream 1.4.6 or below can register an own converter to prevent the unmarshalling of the currently know critical types of the Java runtime. It is in fact an updated version of the workaround for CVE-2013-7285:

java
xstream.registerConverter(new Converter() {
  public boolean canConvert(Class type) {
    return type != null && (type == java.beans.EventHandler.class || type == java.lang.ProcessBuilder.class || type == java.lang.Void.class || void.class || type.getName().equals("javax.imageio.ImageIO$ContainsFilter") || Proxy.isProxy(type));
  }

  public Object unmarshal(HierarchicalStreamReader reader, UnmarshallingContext context) {
    throw new ConversionException("Unsupported type due to security reasons.");
  }

  public void marshal(Object source, HierarchicalStreamWriter writer, MarshallingContext context) {
    throw new ConversionException("Unsupported type due to security reasons.");
  }
}, XStream.PRIORITY_LOW);

Credits

Chen L found and reported the issue to XStream and provided the required information to reproduce it. He was supported by Zhihong Tian and Hui Lu, both from Guangzhou University.

References

See full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for CVE-2020-26217.

For more information

If you have any questions or comments about this advisory:

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Java / Kotlin (Maven) com.thoughtworks.xstream:xstream < 1.4.14-java7 1.4.14-java7

References

CVSS score 8/10
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
Weakness (CWE)
CWE-78
Platform
Java / Kotlin (Maven)
Package
com.thoughtworks.xstream:xstream
Disclosed
16.11.2020
Updated
11.10.2026 12:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-mw36-7c6c-q4q2 - CC BY 4.0

Vulnerability history: com.thoughtworks.xstream:xstream

All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (37) in the archive
Total entries
37
First → latest
05.2019 11.2024
Without a fix
0
Exploited in attacks
1

Severity breakdown

  • Critical 2
  • High 22
  • Medium 13

Disclosures per year

  1. 2019: 2
  2. 2020: 5
  3. 2021: 26
  4. 2022: 3
  5. 2023: 0
  6. 2024: 1
  7. 2025: 0
  8. 2026: 0
Severity:
  1. High · 8.2 CVE-2022-41966 < 1.4.20 1.4.20
  2. High · 8.5 CVE-2021-39139 < 1.4.18 1.4.18
  3. High · 8.5 CVE-2021-39141 < 1.4.18 1.4.18
  4. High · 8.5 Exploited in attacks CVE-2021-39144 < 1.4.18 1.4.18
  5. High · 8.5 CVE-2021-39145 < 1.4.18 1.4.18
  6. High · 8.5 CVE-2021-39146 < 1.4.18 1.4.18
  7. High · 8.5 CVE-2021-39147 < 1.4.18 1.4.18
  8. High · 8.5 CVE-2021-39148 < 1.4.18 1.4.18
  9. High · 8.5 CVE-2021-39149 < 1.4.18 1.4.18
  10. High · 8.5 CVE-2021-39151 < 1.4.18 1.4.18
  11. High · 8.5 CVE-2021-39153 < 1.4.18 1.4.18
  12. High · 8.5 CVE-2021-39154 < 1.4.18 1.4.18
  13. High · 7.5 CVE-2021-29505 < 1.4.17 1.4.17
  14. High · 7.5 CVE-2021-21341 < 1.4.16 1.4.16
  15. XStream can be used for Remote Code Execution this entry
    High · 8.0 CVE-2020-26217 < 1.4.14-java7 1.4.14-java7
  16. High · 7.5 CVE-2017-7957 < 1.4.10 1.4.10
  17. High · 7.5 CVE-2016-3674 < 1.4.9 1.4.9
  18. Critical · 9.8 CVE-2019-10173 >= 1.4.10, < 1.4.11 1.4.11
  19. Critical · 9.8 CVE-2013-7285 < 1.4.7, >= 1.4.10, < 1.4.11 1.4.7, 1.4.11

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.