LiveActive security incident?Get immediate response
CVE Record

CVE-2021-39154: XStream is vulnerable to an Arbitrary Code Execution attack

XStream is a simple library to serialize objects to XML and back again. In affected versions this vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. XStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.

HighCVSS 8.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-39154 affects XStream, a Java XML serialization library. If an application processes attacker-controlled XML with vulnerable XStream defaults, a remote attacker may cause arbitrary code execution. The issue is serious, but sources do not show known active exploitation, and properly configured type allowlisting reduces exposure.

Executive priority

Prioritize remediation for externally reachable Java services and vendor products that deserialize XML. This is high business risk because successful exploitation could compromise confidentiality, integrity, and availability, but urgency should be based on confirmed XStream usage and whether untrusted XML reaches it.

Technical view

Affected XStream versions before 1.4.18 may deserialize manipulated input in a way that loads and executes arbitrary code from a remote host. The CVSS 3.1 score is 8.5 with network attack vector, low privileges, no user interaction, high complexity, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely in Java applications or bundled products using XStream before 1.4.18 to process untrusted XML. Internet-facing APIs, import features, message processors, or file upload workflows raise concern. Systems using XStream’s security framework with a minimal required type allowlist are less likely to be affected.

Exploitation context

The bundle says remote exploitation depends on manipulating the processed input stream and has high attack complexity. KEV is false, and no provided source confirms active exploitation. Treat this as a high-impact deserialization risk requiring a reachable vulnerable XStream path, not as proven mass exploitation.

Researcher notes

Focus validation on deserialization reachability, version provenance, and XStream security framework configuration. Do not assume all XStream installations are exploitable: the advisory states users with a minimal required type whitelist were not affected. Evidence for active exploitation is absent from the supplied sources.

Mitigation direction

  • Upgrade XStream to 1.4.18 or later, or apply vendor backported packages.
  • Configure XStream security with an allowlist of only required application types.
  • Identify downstream products that bundle XStream and follow their vendor advisories.
  • Reduce or remove XStream processing of untrusted XML where possible.
  • Prioritize fixes for externally reachable import, API, and message-processing paths.

Validation and detection

  • Inventory direct and transitive XStream dependencies, including packaged libxstream-java.
  • Confirm deployed versions are 1.4.18 or vendor-patched equivalents.
  • Review XStream configuration for minimal explicit type allowlisting.
  • Map all endpoints and jobs that deserialize XML from untrusted sources.
  • Check Debian, Fedora, Oracle, and NetApp advisories where those ecosystems apply.
Prepared
Confidence
high
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-434: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-39154 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
12Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.5CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H1.86Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.5High
CVSS 3.1 vector shape for CVE-2021-39154Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
x-streamxstream< 1.4.18Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-434 · source CWE mapping

Unrestricted Upload of File with Dangerous Type

Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.