CVE-2019-18212 json
XMLLanguageService.java in XML Language Server (aka lsp4xml) before 0.9.1, as used in Red Hat XML Language Support (aka vscode-xml) before…
published 2019-10-23 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-8012
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.8%
- EPSS 2.8% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
XMLLanguageService.java in XML Language Server (aka lsp4xml) before 0.9.1, as used in Red Hat XML Language Support (aka vscode-xml) before 0.9.1 for Visual Studio and other products, allows a remote attacker to write to arbitrary files via Directory Traversal.
Patch / fix
- xml_language_server_project xml_server_project 0.9.1
- github.com/angelozerr/lsp4xml#567 pull request
- github.com/redhat-developer/vscode-xml/ advisory
Exploit prediction
2.84% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- shielder.it https://www.shielder.it/blog/dont-open-that-xml-xxe-to-rce-in-xml-plugins-for-vs-code-eclipse-theia/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/angelozerr/lsp4xml/pull/567
patch, third-party-advisory
-
github.com
/redhat-developer/vscode-xml/
patch, third-party-advisory
-
shielder.it
/blog/dont-open-that-xml-xxe-to-rce-in-xml-plugins-for-vs-code-eclipse-theia/
exploit, third-party-advisory
-
github.com
/angelozerr/lsp4xml/
product
-
marketplace.visualstudio.com
/items?itemName=redhat.vscode-xml
third-party-advisory
-
github.com
/angelozerr/lsp4xml/blob/master/CHANGELOG.md#others
release-notes, third-party-advisory
Sources
- CVE List CVE-2019-18212
- NVD CVE-2019-18212
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.