How severe is GHSA-j9h8-phrw-h4fh?

GHSA-j9h8-phrw-h4fh has a CVSS score of 8.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-j9h8-phrw-h4fh?

GHSA-j9h8-phrw-h4fh affects the following packages: com.thoughtworks.xstream:xstream (Maven). Ecosystems affected: Maven.

How do I fix GHSA-j9h8-phrw-h4fh?

Update com.thoughtworks.xstream:xstream to 1.4.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j9h8-phrw-h4fh is resolved across your whole dependency graph.

How do I detect GHSA-j9h8-phrw-h4fh in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.thoughtworks.xstream:xstream, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-j9h8-phrw-h4fh if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-j9h8-phrw-h4fh actively exploited in the wild?

Yes. There are 6 known exploit references for GHSA-j9h8-phrw-h4fh, including 6 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-j9h8-phrw-h4fh?

GHSA-j9h8-phrw-h4fh has an EPSS (Exploit Prediction Scoring System) score of 98.1%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is GHSA-j9h8-phrw-h4fh in the CISA Known Exploited Vulnerabilities catalog?

Yes. GHSA-j9h8-phrw-h4fh (XStream Remote Code Execution Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2023-03-10. CISA required all US federal civilian agencies to remediate this vulnerability by 2023-03-31. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is GHSA-j9h8-phrw-h4fh?

GHSA-j9h8-phrw-h4fh is classified as Code Injection (CWE-94), Deserialization of Untrusted Data (CWE-502), Missing Authentication (CWE-306). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for GHSA-j9h8-phrw-h4fh?

A Nuclei detection template exists for GHSA-j9h8-phrw-h4fh, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-j9h8-phrw-h4fh published, and has it been updated?

GHSA-j9h8-phrw-h4fh was published on August 25, 2021 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

CISA KEV · ACTIVELY EXPLOITED

HIGH severity

XStream is vulnerable to a Remote Command Execution attackGHSA-j9h8-phrw-h4fh

HIGH

GHSA-j9h8-phrw-h4fh is a high-severity (CVSS 8.5) Code Injection vulnerability in com.thoughtworks.xstream:xstream. It is in CISA's Known Exploited Vulnerabilities catalog (added 2023-03-10) — treat it as actively exploited and patch now. A fix is available for com.thoughtworks.xstream:xstream — see the affected versions and patch details below.

Also known asCVE-2021-39144

Published

Aug 25, 2021

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

6 known

Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2023-03-10. Federal agencies were required to remediate by 2023-03-31.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for GHSA-j9h8-phrw-h4fh.

EPSS Exploitation Probability

via FIRST.org ↗

98.1%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-j9h8-phrw-h4fh by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

☕com.thoughtworks.xstream:xstream

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

The vulnerability may allow a remote attacker has sufficient rights to execute commands of the 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.

Patches

XStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.

Workarounds

See workarounds for the different versions covering all CVEs.

References

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

Credits

Ceclin and YXXX from the Tencent Security Response Center found and reported the issue to XStream and provided the required information to reproduce it.

For more information

If you have any questions or comments about this advisory:

Open an issue in XStream
Email us at XStream Google Group

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.thoughtworks.xstream:xstream`	all versions	1.4.18`com.thoughtworks.xstream:xstream:1.4.18`

Affected Products

15 products · 36 configurations

debian linuxdebian

3 versions

9.010.011.0

fedorafedoraproject

3 versions

333435

Application

snapmanagernetapp

all

Application

business activity monitoringoracle

1 version

12.2.1.4.0

Application

commerce guided searchoracle

1 version

11.3.2

Application

communications billing and revenue management elastic charging engineoracle

2 versions

11.312.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.