CVE-2017-18197 is a critical-severity (CVSS 9.8) XML External Entity (XXE) vulnerability in mxgraph. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for mxgraph — see the affected versions and patch details below.
mxGraph vulnerable to XXE attacks
EPSS Exploitation Probability
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
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
mxgraphnpmDescription
In mxGraphViewImageReader.java in mxGraph before 3.7.6, the SAXParserFactory instance in convert() is missing flags to prevent XML External Entity (XXE) attacks, as demonstrated by /ServerView.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | mxgraph | all versions | 3.7.6npm install mxgraph@3.7.6 |
Affected Products
mxgraphjgraphResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mxgraph, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mxgraph to 3.7.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-18197 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2017-18197 in your dependencies?
Find it across npm, including transitive dependencies.