CVE-2017-7957

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 4.9% (91st percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 4.9%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

XStream through 1.4.9, when a certain denyTypes workaround is not used, mishandles attempts to create an instance of the primitive type 'void' during unmarshalling, leading to a remote application crash, as demonstrated by an xstream.fromXML("") call.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
51
EG Risk 51/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation5% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
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
4.9%
EPSS %ILE
91st
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

April 29, 2017

Last Modified

October 8, 2026

Advisory Details (7)

Auto-updated Oct 8, 2026
Patch available. Sources: redhat.
generic

[SECURITY] [DSA 3841-1] libxstream-java

http://www.debian.org/security/2017/dsa-3841
generic

IBM X-Force Exchange

https://exchange.xforce.ibmcloud.com/vulnerabilities/125800
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2017:2889
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2017:2888
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2017:1832
generic

XStream - CVE-2017-7957

http://x-stream.github.io/CVE-2017-7957.html
generic

CVE-2017-7957 - PSIRT.COM

http://www.securityfocus.com/bid/100687

Vendor Advisories for CVE-2017-7957(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpatch2017-10-12redhat
redhatxstream2017-10-12redhat
redhatcamel2017-08-10redhat

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

(7 across 7 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
libxstream-java—
  • every version up to 1.4.9-2: fixed in 1.4.9-2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libxstream-java—
  • every version up to 1.4.9-2: fixed in 1.4.9-2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libxstream-java—
  • every version up to 1.4.9-2: fixed in 1.4.9-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libxstream-java—
  • every version up to 1.4.9-2: fixed in 1.4.9-2
—
Debian:7(1)
PackageVulnerable rangeFix by version rangeDependents
libxstream-java1.4.2-1, 1.4.2-1+deb7u1
  • every version up to 1.4.2-1+deb7u2: fixed in 1.4.2-1+deb7u2
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
libxstream-java1.4.7-2, 1.4.7-2+deb8u1
  • every version up to 1.4.7-2+deb8u2: fixed in 1.4.7-2+deb8u2
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
com.thoughtworks.xstream:xstream0.1 ... 1.4.9 (27 versions)
  • every version up to 1.4.10: fixed in 1.4.10
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-09 20:02 UTCEPSS rescore
  2. 2026-10-08 21:27 UTCEG score recompute
  3. 2026-10-08 21:27 UTCVendor advisory
  4. 2026-10-08 16:36 UTCEPSS rescore
  5. 2026-10-07 23:41 UTCEPSS rescore
  6. 2026-10-06 15:12 UTCEPSS rescore
  7. 2026-10-06 13:14 UTCOSV refresh
  8. 2026-10-05 17:39 UTCEPSS rescore
  9. 2026-10-03 14:21 UTCEPSS rescore
  10. 2026-10-03 14:21 UTCEPSS rescore
  11. 2026-09-30 14:59 UTCEPSS rescore
  12. 2026-09-30 09:40 UTCEG score recompute
  13. 2026-09-28 13:45 UTCEPSS rescore
  14. 2026-09-27 13:40 UTCEPSS rescore
  15. 2026-09-27 13:40 UTCEPSS rescore
  16. 2026-09-26 15:53 UTCEPSS rescore
  17. 2026-09-26 00:19 UTCEPSS rescore
  18. 2026-09-24 13:59 UTCEPSS rescore
  19. 2026-09-23 13:42 UTCEPSS rescore
  20. 2026-09-21 20:27 UTCEPSS rescore
  21. 2026-09-20 20:09 UTCEPSS rescore
  22. 2026-09-19 15:36 UTCEPSS rescore
  23. 2026-09-17 19:22 UTCEPSS rescore
  24. 2026-09-17 19:22 UTCEPSS rescore
  25. 2026-09-16 19:20 UTCOSV refresh
Show 41 more
  1. 2026-09-15 03:05 UTCEPSS rescore
  2. 2026-09-12 14:56 UTCEPSS rescore
  3. 2026-09-11 09:31 UTCEPSS rescore
  4. 2026-09-07 15:56 UTCEPSS rescore
  5. 2026-09-05 15:24 UTCEPSS rescore
  6. 2026-09-04 13:56 UTCEPSS rescore
  7. 2026-09-04 05:02 UTCEPSS rescore
  8. 2026-09-02 14:07 UTCEPSS rescore
  9. 2026-09-02 14:07 UTCEPSS rescore
  10. 2026-09-01 03:31 UTCEPSS rescore
  11. 2026-08-30 19:13 UTCEPSS rescore
  12. 2026-08-28 21:36 UTCEPSS rescore
  13. 2026-08-28 19:23 UTCOSV refresh
  14. 2026-08-27 14:21 UTCEPSS rescore
  15. 2026-08-26 14:41 UTCEPSS rescore
  16. 2026-08-25 13:44 UTCEPSS rescore
  17. 2026-08-23 00:14 UTCEPSS rescore
  18. 2026-08-21 23:44 UTCEPSS rescore
  19. 2026-08-19 16:59 UTCEPSS rescore
  20. 2026-08-18 13:43 UTCEPSS rescore
  21. 2026-08-16 14:51 UTCEPSS rescore
  22. 2026-08-16 02:10 UTCEPSS rescore
  23. 2026-08-15 01:26 UTCEPSS rescore
  24. 2026-08-12 13:46 UTCEPSS rescore
  25. 2026-08-12 07:47 UTCOSV refresh
  26. 2026-08-09 13:42 UTCEPSS rescore
  27. 2026-08-08 16:32 UTCEPSS rescore
  28. 2026-08-07 16:22 UTCEPSS rescore
  29. 2026-08-06 13:42 UTCEPSS rescore
  30. 2026-08-06 13:42 UTCEPSS rescore
  31. 2026-08-05 19:13 UTCEPSS rescore
  32. 2026-08-02 02:23 UTCEPSS rescore
  33. 2026-08-02 02:23 UTCEPSS rescore
  34. 2026-08-01 04:12 UTCEPSS rescore
  35. 2026-07-30 16:24 UTCEPSS rescore
  36. 2026-07-30 01:26 UTCEPSS rescore
  37. 2026-07-28 15:32 UTCEPSS rescore
  38. 2026-07-27 13:04 UTCEG score recompute▲ 7.50
  39. 2026-07-27 13:04 UTCVendor advisory
  40. 2026-07-27 12:57 UTCEG score recompute
  41. 2026-07-27 12:57 UTCVendor advisory

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2017-7957?
CVE-2017-7957 is a high vulnerability published on April 29, 2017. XStream through 1.4.9, when a certain denyTypes workaround is not used, mishandles attempts to create an instance of the primitive type 'void' during unmarshalling, leading to a remote application crash, as demonstrated by an xstream.fromXML("<void/>") call.
When was CVE-2017-7957 disclosed?
CVE-2017-7957 was first published on April 29, 2017, with the most recent update on October 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-7957 actively exploited?
CVE-2017-7957 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.9% probability of exploitation in the next 30 days (91st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-7957?
CVE-2017-7957 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2017-7957?
A fix for CVE-2017-7957 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2017-7957 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-2017-7957

Explore →

Is Your Infrastructure Affected by CVE-2017-7957?

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

Book a Demo →Browse All CVEs