CVE-2016-3674

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: 8%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Multiple XML external entity (XXE) vulnerabilities in the (1) Dom4JDriver, (2) DomDriver, (3) JDomDriver, (4) JDom2Driver, (5) SjsxpDriver, (6) StandardStaxDriver, and (7) WstxDriver drivers in XStream before 1.4.9 allow remote attackers to read arbitrary files via a crafted XML document.

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
8%
EPSS %ILE
94%
KEV
Not listed

Published

May 17, 2016

Last Modified

June 17, 2026

References (22)

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2016-11-28redhat
redhatpatch2016-11-28redhat

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-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libxstream-java—1.4.9-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libxstream-java—1.4.9-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libxstream-java—1.4.9-1—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
libxstream-java1.4.2-11.4.2-1+deb7u1—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
libxstream-java1.4.7-21.4.7-2+deb8u1—
Maven(1)
PackageVulnerable rangeFixed inDependents
com.thoughtworks.xstream:xstream0.1 ... 1.4.8 (26 versions)1.4.9—

Weakness Classification(1)

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

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2016-3674?
CVE-2016-3674 is a high vulnerability published on May 17, 2016. Multiple XML external entity (XXE) vulnerabilities in the (1) Dom4JDriver, (2) DomDriver, (3) JDomDriver, (4) JDom2Driver, (5) SjsxpDriver, (6) StandardStaxDriver, and (7) WstxDriver drivers in XStream before 1.4.9 allow remote attackers to read arbitrary files via a crafted XML document.
When was CVE-2016-3674 disclosed?
CVE-2016-3674 was first published in the National Vulnerability Database on May 17, 2016, 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-2016-3674 actively exploited?
CVE-2016-3674 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 8% probability of exploitation in the next 30 days, which ranks it in the top 5.6% of all scored CVEs.
What is the CVSS score of CVE-2016-3674?
CVE-2016-3674 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-2016-3674?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-3674, 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-2016-3674

Explore →

Is Your Infrastructure Affected by CVE-2016-3674?

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

Start Free Scan →Browse All CVEs