CVE-2017-1000190

CRITICALNVD 9.19.1
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 9.1 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
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 5%CVSS: 9.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

SimpleXML (latest version 2.7.1) is vulnerable to an XXE vulnerability resulting SSRF, information disclosure, DoS and so on.

CVSS v3
9.1
EG Score
9.1(low)
EG Risk
45(Track)
EG Risk 45/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
Severity91% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
5%
EPSS %ILE
91%
KEV
Not listed

Published

November 17, 2017

Last Modified

June 17, 2026

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
simple-xml2.7.1-3
Debian:12(1)
PackageVulnerable rangeFixed inDependents
simple-xml2.7.1-3
Debian:13(1)
PackageVulnerable rangeFixed inDependents
simple-xml2.7.1-3
Debian:14(1)
PackageVulnerable rangeFixed inDependents
simple-xml2.7.1-3
Maven(1)
PackageVulnerable rangeFixed inDependents
org.simpleframework:simple-xml1.4 ... 2.7 (47 versions)2.7.1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 3× 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-26 14:41 UTCEPSS rescore
  2. 2026-08-25 13:44 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-17 13:42 UTCEPSS rescore
  7. 2026-08-16 14:51 UTCEPSS rescore
  8. 2026-08-16 02:10 UTCEPSS rescore
  9. 2026-08-15 01:25 UTCEPSS rescore
  10. 2026-08-12 13:46 UTCEPSS rescore
  11. 2026-08-12 07:47 UTCOSV refresh
  12. 2026-08-11 13:36 UTCEPSS rescore
  13. 2026-08-08 16:32 UTCEPSS rescore
  14. 2026-08-07 16:22 UTCEPSS rescore
  15. 2026-08-06 13:42 UTCEPSS rescore
  16. 2026-08-05 19:12 UTCEPSS rescore
  17. 2026-08-04 15:05 UTCEPSS rescore
  18. 2026-08-02 02:22 UTCEPSS rescore
  19. 2026-08-01 04:11 UTCEPSS rescore
  20. 2026-07-30 16:24 UTCEPSS rescore
  21. 2026-07-30 01:26 UTCEPSS rescore
  22. 2026-07-30 01:26 UTCEPSS rescore
  23. 2026-07-28 15:31 UTCEPSS rescore
  24. 2026-07-27 13:15 UTCEG score recompute

Frequently asked(5)

What is CVE-2017-1000190?
CVE-2017-1000190 is a critical vulnerability published on November 17, 2017. SimpleXML (latest version 2.7.1) is vulnerable to an XXE vulnerability resulting SSRF, information disclosure, DoS and so on.
When was CVE-2017-1000190 disclosed?
CVE-2017-1000190 was first published in the National Vulnerability Database on November 17, 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-1000190 actively exploited?
CVE-2017-1000190 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.9% of all scored CVEs.
What is the CVSS score of CVE-2017-1000190?
CVE-2017-1000190 has a CVSS v3 base score of 9.1 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2017-1000190?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-1000190, 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-1000190

Explore →

Is Your Infrastructure Affected by CVE-2017-1000190?

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