How severe is CVE-2017-1000190?

CVE-2017-1000190 has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2017-1000190?

CVE-2017-1000190 affects the following packages: org.simpleframework:simple-xml (Maven). Ecosystems affected: Maven.

How do I fix CVE-2017-1000190?

Update org.simpleframework:simple-xml to 2.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-1000190 is resolved across your whole dependency graph.

How do I detect CVE-2017-1000190 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.simpleframework:simple-xml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2017-1000190 if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is CVE-2017-1000190 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2017-1000190, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2017-1000190?

CVE-2017-1000190 has an EPSS (Exploit Prediction Scoring System) score of 4.7%, placing it in the 92th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2017-1000190?

CVE-2017-1000190 is classified as XML External Entity (XXE) (CWE-611). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2017-1000190 published, and has it been updated?

CVE-2017-1000190 was published on November 17, 2017 and was last updated on October 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

CVE-2017-1000190 — simple-xml

CRITICAL

CVE-2017-1000190 is a critical-severity (CVSS 9.1) XML External Entity (XXE) vulnerability in org.simpleframework:simple-xml. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.simpleframework:simple-xml — see the affected versions and patch details below.

SimpleXML has XML External Entity (XXE) vulnerability

Also known asGHSA-f5qf-vh69-9q4r

Published

Nov 17, 2017

Updated

Oct 25, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

4.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs92th percentile — riskier than 92% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.simpleframework:simple-xml

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.simpleframework:simple-xml`	all versions	2.7.1`org.simpleframework:simple-xml:2.7.1`

Affected Products

2 products · 2 configurations

Application

solrapache

1 version

8.4.1

Application

simplexmlsimplexml_project

≤ 2.7.1

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

SimpleXML (latest version 2.7.1) is vulnerable to an XXE vulnerability r…

github.comNVDJul 2019

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.simpleframework:simple-xml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.simpleframework:simple-xml to 2.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-1000190 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2017-1000190 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works