LiveActive security incident?Get immediate response
CVE Record

CVE-2021-39139: 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. A user is only affected if using the version out of the box with JDK 1.7u21 or below. However, this scenario can be adjusted easily to an external Xalan that works regardless of the version of the Java runtime. 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-39139 affects XStream, a Java XML serialization library. Vulnerable versions before 1.4.18 can let an attacker turn crafted input into arbitrary code execution in specific configurations. Business risk is highest where applications deserialize XML from untrusted users, partners, queues, or exposed services.

Executive priority

Prioritize remediation for internet-facing or integration-heavy Java services that process XML. The issue can lead to full compromise, but exposure depends strongly on XStream version, whitelist configuration, Java/Xalan context, and whether untrusted input reaches deserialization code.

Technical view

XStream before 1.4.18 relied on a blacklist model that could be bypassed. The advisory describes remote code loading and execution via manipulated input streams, especially default use with JDK 1.7u21 or older, and notes similar risk with external Xalan. Whitelist-based XStream security configuration avoids the affected pattern.

Likely exposure

Exposure is likely in Java applications or products bundling XStream versions earlier than 1.4.18, especially when processing untrusted XML. Systems using a strict minimal-type whitelist are described as not affected. Vendor-packaged environments should be checked against Debian, Fedora, Oracle, and NetApp advisories where applicable.

Exploitation context

The CVE is not listed as KEV in the supplied bundle. Sources describe remote arbitrary code execution, but the provided evidence does not confirm active exploitation. CVSS 3.1 is 8.5 with network attack vector, high complexity, low privileges, no user interaction, and changed scope.

Researcher notes

Focus validation on dependency provenance and deserialization entry points. The public sources identify affected versions and safe whitelist configuration, but do not provide environment-specific detection logic. Treat vendor products separately because they may embed XStream and require vendor-supplied updates rather than only application dependency upgrades.

Mitigation direction

  • Upgrade XStream to 1.4.18 or later where the library is directly managed.
  • Configure XStream security with a whitelist limited to required application types.
  • Apply relevant Debian, Fedora, Oracle, or NetApp security updates for bundled copies.
  • Review vendor guidance for packaged products before assuming a standalone library fix is sufficient.

Validation and detection

  • Inventory direct and transitive XStream dependencies and confirm versions are at least 1.4.18.
  • Identify application paths that deserialize XML from users, integrations, queues, or external files.
  • Confirm XStream uses an explicit minimal-type whitelist, not default permissive behavior.
  • Check runtime packaging against applicable distribution or product security advisories.
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-39139 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-39139Attack 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.