CVE-2023-29495 is a high severity (CVSS 7.5) improper input validation flaw in the BIOS firmware of some Intel NUC kits. A privileged local user may be able to escalate privileges. The NVD record says BIOS versions before IN0048 are affected, so update to IN0048 or later.
What's affected
The NVD record lists the Intel NUC 8 Mainstream-G kits NUC8i7INH and NUC8i5INH and their firmware, with BIOS versions before IN0048 affected. Fixed: IN0048 or later, as implied by the record. Intel's advisory is INTEL-SA-01009.
The Intel advisory page returned an access denied error when fetched for this article, so the details below come from the NVD record and should be checked against Intel's own advisory.
How to check if you're exposed
Read the BIOS version at boot in the BIOS setup screen, or from Windows with this command:
wmic bios get smbiosbiosversion
On Linux, run sudo dmidecode -s bios-version. Compare the result with IN0048.
What to do now
- List NUC8i7INH and NUC8i5INH systems in your inventory.
- Read each BIOS version and flag anything older than IN0048.
- Download the BIOS update from Intel's support site, following the instructions in INTEL-SA-01009.
- Restrict local administrator rights on affected machines until the update is applied.
Why it matters
The record maps the flaw to CWE-20, improper input validation. Firmware that does not check the data handed to it can be pushed into states its authors did not plan for, and firmware runs below the operating system, so a bug there can be hard to see and hard to undo.
The record says a privileged user with local access is needed, which narrows who can use it. Even so, BIOS issues are worth patching on a schedule because a successful change can persist across operating system reinstalls. The CVE is not on the CISA KEV list.
Firmware updates are easy to postpone because they need a reboot and carry a small risk of a failed flash. That is the usual reason a flaw like this stays open for years on desktops that otherwise get every operating system patch. Add the BIOS version to your inventory as its own field, so that a query for anything older than IN0048 returns a list instead of a project.
If you manage the fleet with a vendor tool or a script, make sure the update has stable power and that a rollback path exists before you push it widely. Intel's advisory is the authority for the update package.
The NVD record names only two kit models. Other NUC models have their own advisories and BIOS numbering, so do not assume IN0048 applies to them.
Quick check
Who can exploit this?
Per the record, a privileged user with local access.
How do I fix it?
Install BIOS IN0048 or later from Intel.
Sources
Last reviewed: 19 October 2026.