NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

XStream is vulnerable to a Denial of Service attack due to stack overflow from a manipulated binary input streamGHSA-hfq9-hggm-c56q

HIGHFix: x-stream/xstream@bb838ce

GHSA-hfq9-hggm-c56q is a high-severity (CVSS 7.5) CWE-121 vulnerability in com.thoughtworks.xstream:xstream. A fix is available for com.thoughtworks.xstream:xstream — see the affected versions and patch details below.

Also known asCVE-2024-47072
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-hfq9-hggm-c56q.

EPSS Exploitation Probability

via FIRST.org ↗
2.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs81th percentile — riskier than 81% of all scored CVEsHighest risk
0.00%0.85%1.69%2.54%0.3%2.0%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

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 to terminate the application with a stack overflow error resulting in a denial of service only by manipulating the processed input stream when XStream is configured to use the BinaryStreamDriver.

Patches

XStream 1.4.21 detects the manipulation in the binary input stream causing the the stack overflow and raises an InputManipulationException instead.

Workarounds

The only solution is to catch the StackOverflowError in the client code calling XStream if XStream is configured to use the BinaryStreamDriver.

References

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

Credits

Alexis Challande of Trail Of Bits found and reported the issue to XStream and provided the required information to reproduce it.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavencom.thoughtworks.xstream:xstreamall versions1.4.21com.thoughtworks.xstream:xstream:1.4.21

Detection & mitigation playbook

Open-source dependency

  1. Detect

    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.

  2. Fix

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

  3. Workarounds

    Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This vulnerability in XStream is considered an Important severity rather than Moderate because it exposes applications to a denial of service (DoS) attack with relative ease. By exploiting the flaw in the `BinaryStreamDriver`, an attacker can manipulate the binary input stream to trigger a stack overflow, which…

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for GHSA-hfq9-hggm-c56q (CC BY 4.0)
ProductFixed inAdvisory
OCP-Tools-4.12-RHEL-8jenkins-0:2.479.3.1740464431-3.el8RHSA-2025:2223
OCP-Tools-4.13-RHEL-8jenkins-0:2.479.3.1740464433-3.el8RHSA-2025:2222
OCP-Tools-4.14-RHEL-8jenkins-0:2.479.3.1740109575-3.el8RHSA-2025:2221
OCP-Tools-4.15-RHEL-8jenkins-0:2.479.3.1740051993-3.el8RHSA-2025:2220
OCP-Tools-4.16-RHEL-9jenkins-0:2.479.3.1739896390-3.el9RHSA-2025:2219
OCP-Tools-4.17-RHEL-9jenkins-0:2.479.3.1739859586-3.el9RHSA-2025:2218
Red Hat Build of Keycloaksee advisoryRHSA-2025:2545
Red Hat build of Keycloak 26see advisoryRHSA-2025:8690

Frequently Asked Questions

### Impact The vulnerability may allow a remote attacker to terminate the application with a stack overflow error resulting in a denial of service only by manipulating the processed input stream when XStream is configured to use the BinaryStreamDriver. ### Patches XStream 1.4.21 detects the manipulation in the binary input stream causing the the stack overflow and raises an InputManipulationException instead. ### Workarounds The only solution is to catch the StackOverflowError in the client code calling XStream if XStream is configured to use the BinaryStreamDriver. ### References See full
O3 Security · Impact-Aware SCA

Is GHSA-hfq9-hggm-c56q in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
XStream is vulnerable to a Denial of Service attack due to…