LXCI for VMware

published 2018-11-30 7y ago modified 2026-06-17 4mo ago also EUVD-2018-7950

cvss: 6.5; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 54%
public exploits: 0; none known

In versions prior to 5.5, LXCI for VMware allows an authenticated user to write to any system file due to insufficient sanitization during the upload of a backup file.

Patch / fix

fixed in 1 links 1

Lenovo LXCI for VMware 5.5

support.lenovo.com/us/en/solutions/LEN-23800 advisory

Is CVE-2018-16093 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.73% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	6.5	CVSS:3.0/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

Affected products

Lenovo LXCI for VMware

Classification

Weakness

CWE-434 Unrestricted Upload of File with Dangerous Type

References

support.lenovo.com /us/en/solutions/LEN-23800
patch, vendor-advisory

Sources

CVE List CVE-2018-16093
NVD CVE-2018-16093

Fencer Intel 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.