CVE-2020-26122 json
Inspur NF5266M5 through 3.21.2 and other server M5 devices allow remote code execution via administrator privileges.
published 2020-12-07 5 y ago modified 2026-06-17 4 mo ago also EUVD-2020-18752
- cvss
- 7.2
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 0
- none known
Summary
Inspur NF5266M5 through 3.21.2 and other server M5 devices allow remote code execution via administrator privileges. The Baseboard Management Controller (BMC) program of INSPUR server is weak in checking the firmware and lacks the signature verification mechanism, the attacker who obtains the administrator's rights can control the BMC by inserting malicious code into the firmware program and bypassing the current verification mechanism to upgrade the BMC.
Patch / fix
- inspur nf8480m5_firmware 1.19.34
- inspur nf8260m5_firmware 1.19.34
- inspur ns5162m5_firmware 4.5.3
- inspur ns5488m5_firmware 1.19.33
- inspur ns5484m5_firmware 1.19.33
- inspur ns5482m5_firmware 1.19.33
- inspur nf5280m5_firmware 4.26.6
- inspur nf5468m5_firmware 1.18.51
- inspur nf5488m5-d_firmware 1.18.51
- inspur nf5180m5_firmware 4.18.2
- inspur nf5270m5_firmware 4.9.1
- inspur nf5260m5_firmware 3.8.0
- inspur nf5266m5_firmware 3.21.3
- inspur nf5466m5_firmware 4.28.0
- inspur nf5486m5_firmware 3.22.0
Exploit prediction
1.21% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-347 Improper Verification of Cryptographic Signature
References
-
en.inspur.com
/en/security_bulletins/security_advisory2/2543921/index.html
vendor-advisory
-
en.inspur.com
/en/2487134/index.html
broken-link
Sources
- CVE List CVE-2020-26122
- NVD CVE-2020-26122
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.