| CVE-2019-5392US | medium5.3 | 7.16% (94th) | Exploit | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-11945US | critical9.8 | 78.6% (100th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2017-5791US | critical9.8 | 68.9% (99th) | — | ✗no fix | 2017-10-11 | ≤ HPE Intelligent Management Center (IMC) PLAT |
| CVE-2018-7123US | high7.5 | 57.7% (99th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-5355US | high7.5 | 54.0% (99th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-11944US | critical9.8 | 13.3% (96th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-5356US | critical9.8 | 10.9% (96th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-11949US | critical9.8 | 8.11% (95th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-5387US | critical9.8 | 8.11% (95th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-5358US | critical9.8 | 8.11% (95th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-5352US | critical9.8 | 8.11% (95th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-5367US | critical9.8OT elevated | 8.04% (95th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2018-7124US | critical9.8 | 8.04% (95th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2018-7121US | critical9.8 | 7.63% (95th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-11956US | high8.8 | 5.71% (93rd) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-11950US | high8.8 | 5.71% (93rd) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-5350US | high8.8 | 5.71% (93rd) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-5347US | critical9.8 | 5.40% (93rd) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-11957US | high8.1 | 5.16% (92nd) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-5390US | critical9.8 | 4.36% (91st) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-11986US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-11985US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-11969US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-11965US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-11964US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-11963US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-11962US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-11961US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-11960US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-11959US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-11958US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-11955US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-11954US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-11953US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-11952US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-11951US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-5389US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-5388US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-5386US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-5385US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-5384US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-5383US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-5382US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-5381US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-5380US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-5379US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-5378US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-5377US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-5373US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |
| CVE-2019-5372US | high8.8 | 3.57% (89th) | — | ✗no fix | 2019-06-05 | ≤ 7.3 E0506P09 and earlier |