Advisory record · GHSA-j9h8-phrw-h4fh

XStream is vulnerable to a Remote Command Execution attack

CVSS 8.5 HighCriticalIn CISA KEVEPSS 0.98 · 99th percentile

Critical, because:

  • In CISA’s KEV catalogue since 10 Mar 2023: it is known to be exploited.
  • CVSS score 8.5 (7.0 or more) and EPSS 0.98 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 25 Aug 2021, 14:48 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
com.thoughtworks.xstream:xstreamMaven<1.4.181.4.18
Identifiers
GHSA-j9h8-phrw-h4fh · CVE-2021-39144
Weakness (CWE)
CWE-94 · CWE-306 · CWE-502
Published
25 Aug 2021
Updated
8 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

XStream versions before 1.4.18 are vulnerable to remote command execution. An attacker with sufficient rights could run commands on the host by manipulating the input stream that XStream processes. Upgrade to XStream 1.4.18, which no longer uses a blacklist by default; users who configured XStream's security framework with a whitelist of minimal required types are not affected.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.5 High 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Listed since 10 Mar 2023: known to be exploited.
  • EPSS 0.98, the 99th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:20 UTC First seen by agentprime
  2. 31 Oct 2026, 14:20 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.