CVE-2017-7957

HIGHNVD 7.57.5
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 5%CVSS: 7.5Exploit: None knownExposed: 0

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.5(low)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

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%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
5%
EPSS %ILE
91%
KEV
Not listed

Published

April 29, 2017

Last Modified

June 17, 2026

References (18)

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 / EcosystemFixed in / 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 rangeFixed inDependents
libxstream-java—1.4.9-2—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libxstream-java—1.4.9-2—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libxstream-java—1.4.9-2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libxstream-java—1.4.9-2—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
libxstream-java1.4.2-1, 1.4.2-1+deb7u11.4.2-1+deb7u2—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
libxstream-java1.4.7-2, 1.4.7-2+deb8u11.4.7-2+deb8u2—
Maven(1)
PackageVulnerable rangeFixed inDependents
com.thoughtworks.xstream:xstream0.1 ... 1.4.9 (27 versions)1.4.10—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 26× 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-08-25 13:44 UTCEPSS rescore
  2. 2026-08-23 00:14 UTCEPSS rescore
  3. 2026-08-21 23:44 UTCEPSS rescore
  4. 2026-08-19 16:59 UTCEPSS rescore
  5. 2026-08-18 13:43 UTCEPSS rescore
  6. 2026-08-16 14:51 UTCEPSS rescore
  7. 2026-08-16 02:10 UTCEPSS rescore
  8. 2026-08-15 01:26 UTCEPSS rescore
  9. 2026-08-12 13:46 UTCEPSS rescore
  10. 2026-08-12 07:47 UTCOSV refresh
  11. 2026-08-09 13:42 UTCEPSS rescore
  12. 2026-08-08 16:32 UTCEPSS rescore
  13. 2026-08-07 16:22 UTCEPSS rescore
  14. 2026-08-06 13:42 UTCEPSS rescore
  15. 2026-08-06 13:42 UTCEPSS rescore
  16. 2026-08-05 19:13 UTCEPSS rescore
  17. 2026-08-02 02:23 UTCEPSS rescore
  18. 2026-08-02 02:23 UTCEPSS rescore
  19. 2026-08-01 04:12 UTCEPSS rescore
  20. 2026-07-30 16:24 UTCEPSS rescore
  21. 2026-07-30 01:26 UTCEPSS rescore
  22. 2026-07-28 15:32 UTCEPSS rescore
  23. 2026-07-27 13:04 UTCEG score recompute▲ 7.50
  24. 2026-07-27 13:04 UTCVendor advisory
  25. 2026-07-27 12:57 UTCEG score recompute
Show 1 more
  1. 2026-07-27 12:57 UTCVendor advisory

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 in the National Vulnerability Database on April 29, 2017, with the most recent update on June 17, 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 5% probability of exploitation in the next 30 days, which ranks it in the top 8.5% of all scored CVEs.
What is the CVSS score of CVE-2017-7957?
CVE-2017-7957 has a CVSS v3 base score of 7.5 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2017-7957?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-7957, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs