Skip to main content
CVE-2021-29505VulnerabilityPublished Updated

CVE-2021-29505: x-stream xstream · Code Injection

Affects x-stream xstreamSource CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · 77% EPSS · CVSS 7.5 High : upgrade to 1.4.17 as a priority.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
77.2% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.4.17
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 May 2021

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade com.thoughtworks.xstream/xstream to 1.4.17.

Affected software

ProductAffectedFixed in
Mavencom.thoughtworks.xstream/xstreampkg:maven/com.thoughtworks.xstream/xstreamOther threatsAffected
  • <1.4.17
Fixed in
  • 1.4.17

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate upgrade to XStream version 1.4.17 or later to ensure the vulnerability is patched. 2. Implement strict security framework configurations in XStream by enabling whitelisting of only the minimal required classes for deserialization, thereby preventing processing of malicious payloads. 3. Conduct a thorough audit of all Java applications using XStream to identify vulnerable versions and usage patterns. 4. Restrict access to interfaces or services that accept XML input for deserialization, applying network segmentation and access controls to limit exposure. 5. Employ runtime application self-protection (RASP) or Web Application Firewalls (WAFs) with rules to detect and block suspicious XML payloads indicative of exploitation attempts. 6. Monitor logs and network traffic for unusual deserialization activity or anomalies related to XStream usage. 7. Educate developers and security teams about secure deserialization practices and the risks associated with processing untrusted data. 8. Incorporate deserialization security checks into the software development lifecycle and continuous integration pipelines to prevent reintroduction of vulnerable code.

Description

XStream is software for serializing Java objects to XML and back again. A vulnerability in XStream versions prior to 1.4.17 may allow a remote attacker has sufficient rights to execute commands of the host only by manipulating the processed input stream. No user who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types is affected. The vulnerability is patched in version 1.4.17.

References

Community reviews

Loading reviews…