Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain leaked Boot Guard signing keys
-
DeliverySign malicious UEFI firmware image
-
ExploitPhysically reflash target SPI chip
-
ExecutionBootkit passes Boot Guard verification
-
ImpactPersistent pre-OS platform compromise
Vulnerability Assessment
| Exploitation Conditions | Exploitation requires that the attacker possess the Boot Guard and Boot Policy Manifest private signing keys that were inadvertently shipped inside Clevo's UEFI update packages (e.g., B10717.exe), and the ability to deliver a forged firmware image to a target. Per the CVSS physical vector (AV:P), the limiting factor is physical access to perform SPI/firmware reprogramming - this is NOT remotely exploitable. Only Clevo-based systems whose Boot Guard trust anchors correspond to the leaked keys are affected; systems using different OEM keys or with the keys revoked/rotated are not. The decisive mitigating factor is the physical-access requirement, which confines realistic exploitation to targeted, insider, supply-chain, or evil-maid contexts rather than opportunistic remote attacks. |
| Impact | Conflicting signals make this a high-impact but low-likelihood issue rather than an active emergency. The CVSS 7.6 (HIGH) reflects total loss of boot-chain confidentiality, integrity, and availability with a scope change (S:C), but the attack vector is physical (AV:P), which sharply constrains real-world exploitability. EPSS is only 0.26% (16th percentile) and the CVE is NOT on the CISA KEV list, so there is no evidence of active or widespread exploitation. No public exploit code was identified in the provided data, though the vulnerability is unusual in that the enabling artifact - the private Boot Guard/BPM signing keys - is itself the leaked secret, so the hardest part of forging trusted firmware (key possession) is already satisfied for anyone who obtained the B10717.exe package. The low EPSS despite the severe technical impact is consistent with the physical/targeted nature of the threat (evil-maid, supply-chain, or insider scenarios) rather than mass remote exploitation. Bottom line: a genuine integrity concern warranting key rotation and firmware remediation, but not an immediate drop-everything priority absent physical exposure of affected Clevo-based systems. |
| Exploit ScenarioDerived | An attacker who extracted the leaked Boot Guard/BPM private keys from Clevo's publicly distributed update package (e.g., B10717.exe) crafts a malicious UEFI firmware image and signs it so it passes platform verification. With physical access to a target Clevo-based laptop, they reflash the SPI chip with the forged firmware, installing a bootkit that survives Boot Guard checks and OS reinstallation. No public exploit tool was identified, but the leaked keys remove the primary barrier to forging trusted firmware. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Clevo UEFI firmware update packages, including B10717.exe, exposed private signing keys for Boot Guard and Boot Policy Manifest verification, allowing an attacker who possesses those keys and physical SPI/firmware access to sign malicious firmware that affected Clevo-based systems may trust during early boot. No public exploit identified at time of analysis, and EPSS is 0.26% (16th percentile), reflecting a high-impact but low-likelihood issue. The CVSS vector is AV:P/PR:N, so exploitation is unauthenticated but requires physical access and is confined to targeted, insider, supply-chain, or evil-maid scenarios rather than remote attacks.
RemediationAI
No vendor-released patch identified at time of analysis. Primary remediation is to obtain and apply a Clevo firmware update that revokes or rotates the exposed Boot Guard and Boot Policy Manifest signing keys, where Clevo offers such an update. If no key-revocation or key-rotation update is available, treat affected Clevo systems as having compromised firmware trust anchors and limit their use for high-assurance or high-value workloads, isolate them from sensitive networks, and rely on physical security controls such as locked cases, tamper-evident seals, chassis intrusion detection, and restricted SPI programming access; these reduce evil-maid and insider opportunities but do not eliminate risk if an attacker already has physical access. Firmware attestation against known-good hashes and TPM-backed measured boot can help detect unauthorized firmware changes, but if malicious firmware is validly signed with the leaked key, attestation may not flag it unless expected measurements are independently updated. Consult the Binarly advisory at https://www.binarly.io/advisories/brly-2025-002 and CERT/CC VU#538470 at https://www.kb.cert.org/vuls/id/538470 for vendor guidance and key-revocation instructions.
Affected ProductsAI
Clevo UEFI firmware update packages, specifically B10717.exe, and potentially other Clevo update packages that contain the same private Boot Guard and Boot Policy Manifest signing keys. No CPE identifiers were supplied in the input. Affected systems are Clevo-based platforms whose Boot Guard trust anchors match the exposed keys; systems using different OEM keys or systems where the exposed keys have been revoked or rotated are not affected. See the Binarly advisory BRLY-2025-002 at https://www.binarly.io/advisories/brly-2025-002 and CERT/CC VU#538470 at https://www.kb.cert.org/vuls/id/538470.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected technology is UEFI firmware and Boot Guard verified boot, where private signing keys authorize the initial boot firmware and its Boot Policy Manifest. The root cause is not a memory-safety bug but information disclosure of private cryptographic keys inadvertently shipped inside Clevo firmware update packages, notably B10717.exe; no CWE was provided, but the weakness aligns with exposed private key material. With the leaked keys, a threat actor can produce firmware signed as trusted by systems whose Boot Guard trust anchors correspond to those keys. The CVSS vector AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H shows scope change and high confidentiality, integrity, and availability impact once the boot chain is subverted, but the physical attack vector means the attacker must already have the leaked keys and physical SPI/firmware reprogramming capability. The Binarly advisory BRLY-2025-002 and CERT/CC VU#538470 are the primary references.
Know when Uefi gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Forging trusted firmware with the leaked keys requires physical SPI reflash (AV:P) and no credentials (PR:N); defeating Boot Guard compromises the whole platform beyond the firmware component (S:C) with full C/I/A loss.
Primary rating from Vendor (cert).
CVSS VectorVendor: cert
DescriptionCVE.org
Clevo’s UEFI firmware update packages, including B10717.exe, inadvertently contained private signing keys used for Boot Guard and Boot Policy Manifest verification. The exposure of these keys could allow attackers to sign malicious firmware that appears trusted by affected systems, undermining the integrity of the early boot process.
Executive ViewAI
The exposure of private signing keys in Clevo UEFI firmware update packages such as B10717.exe enables attackers with physical SPI access to deploy malicious firmware that affected systems may trust during early boot. No public exploit identified at time of analysis; exploitation is unauthenticated per the CVSS vector but requires physical access and possession of the exposed keys, making this a targeted risk for insider, supply-chain, or evil-maid scenarios rather than a remote mass attack. Leadership should care because firmware-level compromise can persist below the operating system and evade traditional controls, affecting high-value or high-assurance Clevo-based assets; prioritize inventory, physical security, and vendor engagement while no patch is available.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict physical access to affected Clevo systems, enforce SPI flash write protection and firmware integrity monitoring, disable unnecessary firmware update channels, review supply-chain and insider threat controls, and maintain chain-of-custody for high-value assets.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Local privilege-abuse code execution affects Howyar Technologies' SysReturn disk-protection solution in all versions pri
Arbitrary code execution in System Management Mode (SMM) is possible on Insyde UEFI-based devices when a local high-priv
IBM Unified Extensible Firmware Interface (UEFI) on Flex System x880 X6, System x3850 X6, and System x3950 X6 devices al
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB