Skip to main content
CVE-2025-11577VulnerabilityPublished

CVE-2025-11577: Clevo Notebook System Firmware · Use of Hard‑coded Cryptographic Key

Affects Clevo Notebook System FirmwareSource CVE Database V5

0

Not known to be exploited · CVSS 7.6 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

AI-suggested

1. Monitor Clevo’s official channels closely for firmware updates addressing CVE-2025-11577 and apply patches immediately upon release. 2. Restrict physical and local access to devices to trusted personnel only, as exploitation requires local or physical access. 3. Implement strict controls over firmware update processes, including authentication and authorization mechanisms, to prevent unauthorized firmware flashing. 4. Deploy firmware integrity verification tools and endpoint detection solutions capable of detecting unauthorized firmware modifications or anomalies in the boot process. 5. Conduct regular audits of firmware versions across the device fleet to identify and remediate vulnerable systems promptly. 6. Educate IT and security teams about the risks of firmware-level attacks and the importance of secure boot integrity. 7. Consider hardware replacement or isolation strategies for critical systems if patches are delayed or unavailable. 8. Use hardware-based security features such as TPM and Intel Boot Guard configurations to enhance boot process security, ensuring they are correctly enabled and configured. 9. Maintain comprehensive incident response plans that include firmware compromise scenarios. 10. Collaborate with suppliers and service providers to ensure secure firmware management practices throughout the device lifecycle.

Description

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.

References

Community reviews

Loading reviews…