Skip to content
Fencer Intel
critical 9.8

CVE-2020-5955 json

An issue was discovered in Int15MicrocodeSmm in Insyde InsydeH2O before 2021-10-14 on Intel client chipsets.

published 5y ago modified 4mo ago also EUVD-2020-27109

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 72%
public exploits
0
none known

Summary

An issue was discovered in Int15MicrocodeSmm in Insyde InsydeH2O before 2021-10-14 on Intel client chipsets. A caller may be able to escalate privileges.

Patch / fix

  • insyde insydeh2o_uefi_bios 05.04.15.0001, 05.04.21.0068, 05.05.39.0001, 05.10.48.0001, 05.11.26.0015, 05.12.09.0075, 05.21.43.0001, 05.21.51.0040, 05.23.04.0045, 05.23.27.0001, 05.23.45.0023, 05.32.30.0001, 05.32.47.0001, 05.34.09.0030, 05.41.35.0001, 05.42.09.0003, 05.42.11.0026

Is CVE-2020-5955 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

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

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

References

Sources

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.