CVE-2021-33086: Out-of-bounds write in firmware for some Intel(R) NUCs may allow an authenticated user to potentially enable denial of service via local acc
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Out-of-bounds write in firmware for some Intel(R) NUCs may allow an authenticated user to potentially enable denial of service via local access.
- Published
- Nov 17, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- CWE-787
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| intel | nuc m15 laptop kit lapbc510 firmware | cpe:2.3:o:intel:nuc_m15_laptop_kit_lapbc510_firmware |
| intel | nuc m15 laptop kit lapbc510 | cpe:2.3:h:intel:nuc_m15_laptop_kit_lapbc510 |
| intel | nuc m15 laptop kit lapbc710 firmware | cpe:2.3:o:intel:nuc_m15_laptop_kit_lapbc710_firmware |
| intel | nuc m15 laptop kit lapbc710 | cpe:2.3:h:intel:nuc_m15_laptop_kit_lapbc710 |
| intel | nuc 11 compute element cm11ebc4w firmware | cpe:2.3:o:intel:nuc_11_compute_element_cm11ebc4w_firmware |
| intel | nuc 11 compute element cm11ebc4w | cpe:2.3:h:intel:nuc_11_compute_element_cm11ebc4w |
| intel | nuc 11 compute element cm11ebi38w firmware | cpe:2.3:o:intel:nuc_11_compute_element_cm11ebi38w_firmware |
| intel | nuc 11 compute element cm11ebi38w | cpe:2.3:h:intel:nuc_11_compute_element_cm11ebi38w |
| intel | nuc 11 compute element cm11ebi58w firmware | cpe:2.3:o:intel:nuc_11_compute_element_cm11ebi58w_firmware |
| intel | nuc 11 compute element cm11ebi58w | cpe:2.3:h:intel:nuc_11_compute_element_cm11ebi58w |
| intel | nuc 11 compute element cm11ebi716w firmware | cpe:2.3:o:intel:nuc_11_compute_element_cm11ebi716w_firmware |
| intel | nuc 11 compute element cm11ebi716w | cpe:2.3:h:intel:nuc_11_compute_element_cm11ebi716w |
and 188 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- intel nuc 10 performance kit nuc10i3fnh firmwarebefore fncml.0052
- intel nuc 10 performance kit nuc10i3fnhf firmwarebefore fncml.0052
- intel nuc 10 performance kit nuc10i3fnhfa firmwarebefore fncml.0052
- intel nuc 10 performance kit nuc10i3fnhja firmwarebefore fncml.0052
- intel nuc 10 performance kit nuc10i3fnk firmwarebefore fncml.0052
- intel nuc 10 performance kit nuc10i5fnh firmwarebefore fncml.0052
- intel nuc 10 performance kit nuc10i5fnhca firmwarebefore fncml.0052
- intel nuc 10 performance kit nuc10i5fnhf firmwarebefore fncml.0052
- intel nuc 10 performance kit nuc10i5fnhj firmwarebefore fncml.0052
- intel nuc 10 performance kit nuc10i5fnhja firmwarebefore fncml.0052
- intel nuc 10 performance kit nuc10i5fnk firmwarebefore fncml.0052
- intel nuc 10 performance kit nuc10i5fnkp firmwarebefore fncml.0052
- intel nuc 10 performance kit nuc10i5fnkpa firmwarebefore fncml.0052
- intel nuc 10 performance kit nuc10i7fnh firmwarebefore fncml.0052
- intel nuc 10 performance kit nuc10i7fnhaa firmwarebefore fncml.0052
- intel nuc 10 performance kit nuc10i7fnhc firmwarebefore fncml.0052
- intel nuc 10 performance kit nuc10i7fnhja firmwarebefore fncml.0052
- intel nuc 10 performance kit nuc10i7fnk firmwarebefore fncml.0052
- intel nuc 10 performance kit nuc10i7fnkp firmwarebefore fncml.0052
- intel nuc 10 performance kit nuc10i7fnkpa firmwarebefore fncml.0052
Versions reported by the vendor
Affected version ranges reported by the assigning authority (intel). Independent of NVD's CPE analysis and usually ahead of it.
n/a Intel(R) NUCs
- See referencesaffected
Same product
intel: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-40250Stack overflow vulnerability in SMI handler on SmmSmbiosElog.35Monitor
- CVE-2022-40261SMM memory corruption vulnerability in OverClockSmiHandler SMM driver32Monitor
- CVE-2022-26873The stack buffer overflow vulnerability in PlatformInitAdvancedPreMem leads to arbitrary code execution during PEI phase.32Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-0054Jun 9, 2021 · Improper buffer restrictions in system firmware for some Intel(R) NUCs may allow a privileged user to potentially enable escalation of privi26Monitor
- ← EarlierCVE-2021-0067Jun 9, 2021 · Improper access control in system firmware for some Intel(R) NUCs may allow a privileged user to potentially enable escalation of priv26Monitor
- Later →CVE-2022-40246Sep 20, 2022 · Arbitrary write vulnerability in SbPei module leads to arbitrary code execution during PEI phase.28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-21-0930 · Nov 18, 2021(Intel Güvenlik Zafiyeti)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.