Insecure default variable initialization in firmware for some Intel(R) NUCs may allow an authenticated user to potentially enable escalatio…

published 2020-11-12 5y ago modified 2026-06-17 4mo ago also EUVD-2020-4648

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

Insecure default variable initialization in firmware for some Intel(R) NUCs may allow an authenticated user to potentially enable escalation of privilege via local access.

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

CVSS scores

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

Affected products

n/a Intel(R) NUCs

Classification

Weakness

CWE-1188 Initialization of a Resource with an Insecure Default

References

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

Sources

CVE List CVE-2020-12336
NVD CVE-2020-12336

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.