Security readout for executives and security teams
Plain-English summary
XStream versions before 1.4.18 can turn malicious XML input into code execution in some configurations. The risk is highest where applications process attacker-controlled XML with XStream and have not restricted allowed types. Proper allowlisting materially reduces exposure.
Executive priority
Treat as high priority for externally reachable or partner-facing systems that ingest XML. Prioritize dependency upgrades and configuration review, especially in Java services and vendor products where XStream may be bundled.
Technical view
The issue is in XStream deserialization and is associated with CWE-502 and CWE-434. A remote attacker with low privileges may manipulate the processed input stream to load and execute arbitrary code from a remote host. CVSS 3.1 is 8.5 high, with high attack complexity and changed scope.
Likely exposure
Java applications, services, or bundled products using x-stream XStream versions before 1.4.18 are potentially exposed when they process untrusted XML. Exposure is reduced where XStream's security framework uses a minimal type whitelist.
Exploitation context
The bundle does not cite active exploitation, and KEV is false. The advisory describes remote code execution through manipulated input, but exploitation depends on application use of vulnerable XStream processing and security configuration.
Researcher notes
Do not assume all XStream usage is exploitable. Validate reachability, input control, version, and allowlist configuration. The vendor notes users following the recommended minimal whitelist were not affected, and 1.4.18 changed the default security posture away from a blacklist.
Mitigation direction
- Upgrade XStream to 1.4.18 or later where directly managed.
- Apply Debian, Fedora, Oracle, NetApp, or other vendor security updates where XStream is bundled.
- Configure XStream's security framework with a minimal required type whitelist.
- Avoid processing untrusted XML through XStream unless strict allowlisting is enforced.
- Check vendor guidance for affected downstream products and package-specific fixes.
Validation and detection
- Inventory direct and transitive Java dependencies for xstream versions before 1.4.18.
- Review SBOMs and packaged applications for bundled libxstream-java or XStream copies.
- Confirm XStream allowlists only the minimal required application types.
- Identify routes, jobs, or APIs that deserialize attacker-controlled XML with XStream.
- Verify patched package versions against the relevant distribution or vendor advisory.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCWE-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 lookupExecution 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 lookupCVE-2021-39149 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H1.86Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.5HighVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/x-stream/xstream/security/advisories/GHSA-3ccq-5vw3-2p6xCVE reference · x_refsource_CONFIRM
- https://x-stream.github.io/CVE-2021-39149.htmlCVE reference · x_refsource_MISC
- [debian-lts-announce] 20210929 [SECURITY] [DLA 2769-1] libxstream-java security updateCVE reference · mailing-list, x_refsource_MLIST
- FEDORA-2021-fbad11014aCVE reference · vendor-advisory, x_refsource_FEDORA
- FEDORA-2021-d894ca87dcCVE reference · vendor-advisory, x_refsource_FEDORA
- FEDORA-2021-5e376c0ed9CVE reference · vendor-advisory, x_refsource_FEDORA
- DSA-5004CVE reference · vendor-advisory, x_refsource_DEBIAN
- https://www.oracle.com/security-alerts/cpujan2022.htmlCVE reference · x_refsource_MISC
- https://security.netapp.com/advisory/ntap-20210923-0003/CVE reference · x_refsource_CONFIRM
- https://www.oracle.com/security-alerts/cpuapr2022.htmlCVE reference · x_refsource_MISC
- https://www.oracle.com/security-alerts/cpujul2022.htmlCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.
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.