Key exchange without entity authentication in the Intel(R) Security Library before version 3.3 may allow an authenticated user to potential…

published 2021-06-09 5y ago modified 2026-06-17 4mo ago also EUVD-2021-2752

cvss: 8.1; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.9%; EPSS 0.9% chance of exploitation in 30 days, percentile 58%
public exploits: 0; none known

Key exchange without entity authentication in the Intel(R) Security Library before version 3.3 may allow an authenticated user to potentially enable escalation of privilege via network access.

Patch / fix

fixed in 1

intel secl-dc 3.3

Is CVE-2021-0133 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.85% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected products

n/a Intel(R) Security Library

References

intel.com /content/www/us/en/security-center/advisory/intel-sa-00521.html
vendor-advisory

Sources

CVE List CVE-2021-0133
NVD CVE-2021-0133

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.