CVE-2021-21342

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 50% (98th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 5.3 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2021-03-22) is not newer than that change (2026-10-07), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2021-0673 (ENISA EUVD) · GHSA-hvv8-336g-rx3m (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 50%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability where the processed stream at unmarshalling time contains type information to recreate the formerly written objects. XStream creates therefore new instances based on these type information. An attacker can manipulate the processed input stream and replace or inject objects, that result in a server-side forgery request. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
76
EG Risk 76/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation50% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
50%
EPSS %ILE
98th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
50% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 23, 2021

Last Modified

October 7, 2026

Advisory Details (10)

Auto-updated Oct 7, 2026
Patch available. Sources: github.
Web page

[SECURITY] [DSA 5004-1] libxstream-java security update

https://www.debian.org/security/2021/dsa-5004
Web page

[SECURITY] Fedora 34 Update: xstream-1.4.18-2.fc34 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/QGXIU3YDPG6OGTDHMBLAFN7BPBERXREB/
Web page

[SECURITY] Fedora 35 Update: xstream-1.4.18-2.fc35 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PVPHZA7VW2RRSDCOIPP2W6O5ND254TU7/
Web page

[SECURITY] Fedora 33 Update: xstream-1.4.18-2.fc33 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/22KVR6B5IZP3BGQ3HPWIO2FWWCKT3DHP/
Web pageMentions a patch (unverified)

[SECURITY] [DLA 2616-1] libxstream-java security update

https://lists.debian.org/debian-lts-announce/2021/04/msg00002.html
GitHub advisoryMentions a patch (unverified)

A Server-Side Forgery Request can be activated unmarshalling with XStream to access data streams from an arbitrary URL referencing a resource in an intranet or the local host · Advisory · x-stream/xstream · GitHub

https://github.com/x-stream/xstream/security/advisories/GHSA-hvv8-336g-rx3m
Web page

XStream - Change History

http://x-stream.github.io/changes.html#1.4.16

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibxstream-java (1.4.11.1-2ubuntu0.1) @ groovy2026-11-01ubuntu
ubuntulibxstream-java (1.4.8-1ubuntu0.1+esm3) @ xenial2026-11-01ubuntu
redhatxstream2021-12-14redhat
redhatpatch2021-12-02redhat
redhatpatch2021-11-23redhat
mavencom.thoughtworks.xstream:xstream @ 1.4.16 (fixes < 1.4.16)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
libxstream-java—
  • every version up to 1.4.15-2: fixed in 1.4.15-2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libxstream-java—
  • every version up to 1.4.15-2: fixed in 1.4.15-2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libxstream-java—
  • every version up to 1.4.15-2: fixed in 1.4.15-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libxstream-java—
  • every version up to 1.4.15-2: fixed in 1.4.15-2
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
libxstream-java1.4.10-1 ... 1.4.9-2+deb9u1 (6 versions)
  • every version up to 1.4.11.1-1+deb9u2: fixed in 1.4.11.1-1+deb9u2
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
com.thoughtworks.xstream:xstream0.1 ... 1.4.9 (40 versions)
  • every version up to 1.4.16: fixed in 1.4.16
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 25× in last 7d / 80× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 224 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 128 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 23:56 UTCEG score recompute
  2. 2026-11-01 23:56 UTCVendor advisory
  3. 2026-11-01 23:56 UTCGHSA enrichmentGHSA-hvv8-336g-rx3m · GitHub severity MODERATE · GitHub CVSS 5.3
  4. 2026-11-01 08:34 UTCGHSA enrichmentGHSA-hvv8-336g-rx3m · GitHub severity MODERATE · GitHub CVSS 5.3
  5. 2026-11-01 08:34 UTCEG score recompute
  6. 2026-11-01 01:58 UTCEG score recompute
  7. 2026-11-01 01:58 UTCVendor advisory
  8. 2026-10-31 16:28 UTCEPSS rescoreEPSS 50% · 98th percentile
  9. 2026-10-31 04:00 UTCEG score recompute
  10. 2026-10-31 04:00 UTCVendor advisory
  11. 2026-10-30 16:29 UTCEPSS rescoreEPSS 50% · 98th percentile
  12. 2026-10-30 06:03 UTCEG score recompute
  13. 2026-10-30 06:03 UTCVendor advisory
  14. 2026-10-29 16:29 UTCEPSS rescoreEPSS 50% · 98th percentile
  15. 2026-10-29 08:06 UTCEG score recompute
  16. 2026-10-29 08:06 UTCVendor advisory
  17. 2026-10-28 16:28 UTCEPSS rescoreEPSS 50% · 98th percentile
  18. 2026-10-28 10:07 UTCEG score recompute
  19. 2026-10-28 10:07 UTCVendor advisory
  20. 2026-10-27 16:28 UTCEPSS rescoreEPSS 50% · 98th percentile
  21. 2026-10-27 11:13 UTCEG score recompute
  22. 2026-10-27 11:13 UTCVendor advisory
  23. 2026-10-26 16:27 UTCEPSS rescoreEPSS 50% · 98th percentile
  24. 2026-10-26 13:16 UTCEG score recompute
  25. 2026-10-26 13:16 UTCVendor advisory
Show 71 more
  1. 2026-10-25 16:28 UTCEPSS rescoreEPSS 50% · 98th percentile
  2. 2026-10-25 15:07 UTCEG score recompute
  3. 2026-10-25 15:07 UTCVendor advisory
  4. 2026-10-24 17:08 UTCEG score recompute
  5. 2026-10-24 17:08 UTCVendor advisory
  6. 2026-10-24 16:28 UTCEPSS rescoreEPSS 50% · 98th percentile
  7. 2026-10-23 19:11 UTCEG score recompute
  8. 2026-10-23 19:11 UTCVendor advisory
  9. 2026-10-23 16:28 UTCEPSS rescoreEPSS 50% · 98th percentile
  10. 2026-10-22 21:10 UTCEG score recompute
  11. 2026-10-22 21:10 UTCVendor advisory
  12. 2026-10-22 16:29 UTCEPSS rescoreEPSS 50% · 98th percentile
  13. 2026-10-21 23:13 UTCEG score recompute
  14. 2026-10-21 23:13 UTCVendor advisory
  15. 2026-10-21 16:28 UTCEPSS rescoreEPSS 50% · 98th percentile
  16. 2026-10-21 01:12 UTCEG score recompute
  17. 2026-10-21 01:12 UTCVendor advisory
  18. 2026-10-20 16:28 UTCEPSS rescoreEPSS 50% · 98th percentile
  19. 2026-10-20 03:13 UTCEG score recompute
  20. 2026-10-20 03:13 UTCVendor advisory
  21. 2026-10-19 16:28 UTCEPSS rescoreEPSS 50% · 98th percentile
  22. 2026-10-19 03:32 UTCEG score recompute
  23. 2026-10-19 03:32 UTCVendor advisory
  24. 2026-10-18 16:28 UTCEPSS rescoreEPSS 50% · 98th percentile
  25. 2026-10-18 05:33 UTCEG score recompute
  26. 2026-10-18 05:33 UTCVendor advisory
  27. 2026-10-17 16:28 UTCEPSS rescoreEPSS 50% · 98th percentile
  28. 2026-10-17 07:22 UTCEG score recompute
  29. 2026-10-17 07:22 UTCVendor advisory
  30. 2026-10-16 16:33 UTCEPSS rescoreEPSS 50% · 98th percentile
  31. 2026-10-16 09:13 UTCEG score recompute
  32. 2026-10-16 09:13 UTCVendor advisory
  33. 2026-10-15 16:28 UTCEPSS rescoreEPSS 50% · 98th percentile
  34. 2026-10-15 08:43 UTCEG score recompute
  35. 2026-10-15 08:43 UTCVendor advisory
  36. 2026-10-14 16:28 UTCEPSS rescoreEPSS 50% · 98th percentile
  37. 2026-10-14 04:58 UTCEG score recompute
  38. 2026-10-14 04:58 UTCVendor advisory
  39. 2026-10-13 16:28 UTCEPSS rescoreEPSS 50% · 98th percentile
  40. 2026-10-13 00:19 UTCVendor advisory
  41. 2026-10-12 19:25 UTCEG score recompute
  42. 2026-10-12 16:29 UTCEPSS rescoreEPSS 50% · 98th percentile
  43. 2026-10-11 23:50 UTCEG score recompute
  44. 2026-10-11 13:43 UTCEPSS rescoreEPSS 50% · 98th percentile
  45. 2026-10-10 19:56 UTCEPSS rescoreEPSS 50% · 98th percentile
  46. 2026-10-09 20:04 UTCEPSS rescoreEPSS 50% · 98th percentile
  47. 2026-10-07 23:44 UTCEPSS rescoreEPSS 50% · 98th percentile
  48. 2026-10-07 19:28 UTCEG score recompute▲ 2.50
  49. 2026-10-07 19:28 UTCVendor advisory
  50. 2026-10-07 19:19 UTCNVD updateCVSS v3 → 9.1 · severity → CRITICAL
  51. 2026-10-07 19:03 UTCEG score recompute
  52. 2026-10-07 19:03 UTCVendor advisory
  53. 2026-10-06 15:13 UTCEPSS rescoreEPSS 50% · 98th percentile
  54. 2026-10-04 23:18 UTCEPSS rescoreEPSS 50% · 98th percentile
  55. 2026-10-03 14:22 UTCEPSS rescoreEPSS 50% · 98th percentile
  56. 2026-10-02 16:22 UTCEPSS rescoreEPSS 50% · 98th percentile
  57. 2026-10-01 19:46 UTCEPSS rescoreEPSS 50% · 98th percentile
  58. 2026-09-30 15:29 UTCEG score recompute
  59. 2026-09-30 15:00 UTCEPSS rescoreEPSS 50% · 98th percentile
  60. 2026-09-27 13:41 UTCEPSS rescoreEPSS 50% · 98th percentile
  61. 2026-09-26 15:54 UTCEPSS rescoreEPSS 50% · 98th percentile
  62. 2026-09-26 06:55 UTCOSV refresh
  63. 2026-09-24 14:00 UTCEPSS rescoreEPSS 50% · 98th percentile
  64. 2026-09-23 13:44 UTCEPSS rescoreEPSS 50% · 98th percentile
  65. 2026-09-22 14:44 UTCEPSS rescoreEPSS 50% · 98th percentile
  66. 2026-09-21 20:28 UTCEPSS rescoreEPSS 50% · 98th percentile
  67. 2026-09-19 15:37 UTCEPSS rescoreEPSS 50% · 98th percentile
  68. 2026-09-18 19:23 UTCEPSS rescoreEPSS 50% · 98th percentile
  69. 2026-09-17 19:23 UTCEPSS rescoreEPSS 50% · 98th percentile
  70. 2026-09-16 14:04 UTCEPSS rescoreEPSS 50% · 98th percentile
  71. 2026-09-15 03:06 UTCEPSS rescoreEPSS 50% · 98th percentile

Frequently asked(5)

What is CVE-2021-21342?
CVE-2021-21342 is a critical-severity vulnerability; its CVE record was published on March 23, 2021. XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability where the processed stream at unmarshalling time contains type information to recreate the formerly written objects. XStream creates therefore new instances based on…
When was the CVE record for CVE-2021-21342 published?
The CVE record for CVE-2021-21342 was published on March 23, 2021. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 7, 2026; the record at its source may have been updated since.
Is CVE-2021-21342 actively exploited?
CVE-2021-21342 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 50% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2021-21342?
CVE-2021-21342 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2021-21342?
A fix for CVE-2021-21342 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2021-21342 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-21342

Explore →

Is Your Infrastructure Affected by CVE-2021-21342?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.