Skip to content

Framework Laptop 13 12th Gen Intel® Core™ — BIOS 3.20

File Release Date
Windows BIOS v3.20 Installer 2026-07-06 Framework_Laptop_13_12th_Gen_Intel_Core_BIOS__3.20.exe SHA256 · 3244FEA111D29103F2E0F95BDB50FC6F567A9441FEBB46C49361FA06B1E51F78
Windows Driver Bundle v3.05 2026-05-12 Framework_Laptop_13_12th_and_13th_Gen_Intel_Core_driver_bundle_W11_v3.05_2026_05_12.exe SHA256 · 8E89972B38BF9EA980789F121F47A613EA46045FF13CA5040C9E761FE91C9947
Wi-Fi Driver for use during Windows Installation 2026-06-18 Framework_W11_OOBE_Wifi_Driver_Package.zip SHA256 · 13d7286531f7fc354bf345ea6f465c76cbba79f783a44b45d4803743022b574a
EFI Shell Update (BIOS v3.20) 2026-07-06 Framework_Laptop_13_12th_Gen_Intel_Core_BIOS__3.20_EFI.zip SHA256 · 88CD52B4BD6440E01B6D9E158A0C5303FE19392159DF3AEC466038F4ECE96D37
3.20
Released 2026-07-06
Stable
Latest
Highlights
  • Updated CSME to 16.1.40.2765v3 Corporate.
  • Update Microcode to 0x43B.
  • Added support for Framework Laptop 13 Pro features - Enabled compatibility for the haptic touchpad, touch panel, and 74W battery.
  • Fixed an issue where the system was unable to boot from partially locked self-encrypting drives (SEDs)
  • Fixed an issue where the Battery Extender status was reported incorrectly following a reboot, hibernation, or shutdown after the timer had expired.
  • Enhanced the Power On AC behavior, allowing the feature to work correctly without requiring the system to boot into the Operating System at least once for initialization.
  • Security Fix: CVE-2025-32008 - Out-of-bounds write in the firmware for the Intel® AMT and Intel® Standard Manageability within Ring 3: User Applications may allow a denial of service. Network adversary with an unauthenticated user combined with a low complexity attack may enable denial of service. This result may potentially occur via network access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (low) impacts. (CVSS 8.6)
  • Security Fix: CVE-2024-24853 - Incorrect behavior order in transition between executive monitor and SMI transfer monitor (STM) in some Intel® Processor may allow a privileged user to potentially enable escalation of privilege via local access. (CVSS 7.2)
  • Security Fix: CVE-2025-20080 - Null pointer dereference in the firmware for some Intel(R) AMT and Intel(R) Standard Manageability within Ring 0: Kernel may allow a denial of service. Network adversary with an unauthenticated user combined with a high complexity attack may enable denial of service. This result may potentially occur via network access when attack requirements are present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts. (CVSS 6.8)
  • Security Fix: CVE-2025-27708 - Out-of-bounds read in the firmware for some Intel(R) Converged Security and Management Engine (CSME) Firmware (FW) within Ring 0: Kernel may allow an information disclosure. System software adversary with a privileged user combined with a low complexity attack may enable data exposure. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (none) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts. (CVSS 4.1)
  • Security Fix: CVE-2025-31648 - Improper handling of values in the microcode flow for some Intel(R) Processor Family may allow an escalation of privilege. Startup code and smm adversary with a privileged user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are present with special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (low), integrity (low) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (low), integrity (low) and availability (none) impacts. (CVSS 3.9)

This BIOS update is a bundle of updates to multiple embedded components in the system. Not all of them use the same version number.

ComponentVersion
SIc.0.75.10
TXT1.18.13.0
Intel CSME16.1.40.2765v3
Updated
Microcode0x43B
Updated
GOP21.0.1061
ECec_320_e12d9a6
Updated
PD0.1.2E
DriverVersion
Intel Chipset10.1.20389.8776
Updated
Intel GNA03.05.00.1574
Intel Management Engine2601.9.16
Updated
Intel Management and Security Status2543.9.0.0
Updated
Intel Serial IO31.100.2351.81
Intel Display31.0.101.7085
Updated
Intel Graphics Command Center1.100.5688.0
Intel Dynamic Tuning9.0.11404.39881
Intel TXT Authenticated Code Module1.18.16.0
Intel PROSet WiFi24.30.1.1
Updated
Intel PROSet Bluetooth24.30.1.1
Updated
Goodix Fingerprint3.12804.1.290
Updated
Realtek Ethernet11013_20_07272023_08042023
SD Card Readerv4_5_10_201
2nd Gen uSD Card Readerv4_5_10_202

You can check your current BIOS version following the steps here to determine if you are on the latest release.

Framework firmware is published to LVFS and updates via fwupd, which ships by default on most modern distributions.

Terminal window
fwupdmgr refresh --force
fwupdmgr get-updates
fwupdmgr update
  1. Download the Framework Laptop 13 12th Gen Intel® Core™ BIOS 3.20 Windows Installer.
  2. Run the .exe and click "Yes" when prompted to reboot.
  3. Wait for the firmware progress bar to complete — the system will reboot automatically. Do not interrupt.
  4. Download and install the Windows Driver Bundle v3.05 for your system if you are currently using a previous Driver Bundle release, or you are installing the Driver Bundle for the first time.

Retimer Updates (Optional)

Retimer updates only need to be performed once. There is no functional impact to port functionality if you do not update. Follow these instructions twice — once for each retimer file.

Framework_Laptop_13_12th_Gen_Intel_Core_Retimer_port_01_310.exe
Framework_Laptop_13_12th_Gen_Intel_Core_Retimer_port_23_310.exe
  1. Update the BIOS first.
  2. Boot into Windows after the BIOS update.
  3. Run the .exe and wait for the firmware update tool to stage the update.

  4. After initialization, the system will restart and update the retimer firmware.

  5. Repeat from step 3 to update the second set of retimers.
  1. Download the EFI Shell Update v3.20.
  2. Extract contents of zip folder to a FAT32 formatted USB drive. Cleanly unmount the drive before physically removing it, otherwise the BIOS update may not function correctly.
  3. Attach a charger to your device while updating.
  4. Boot your system while pressing F12 and boot from the thumb drive.
  5. Let startup.nsh run automatically.
  6. Follow the instructions to install the update.
  • There are two progress bars when updating the BIOS using the EFI update method
  • No display output during the retimer update in standalone mode

Please use the public issue tracker on GitHub to report issues.

If you experience an issue with the update that is related to your system firmware, please post as complete a description as you can, including relevant system information and external peripherals. Please note that we do not currently have a SLA for responding to issues on github, but we will be reviewing them through the bios release process, and will review them for future updates as well.

Please contact support if you have an issue regarding hardware, broken devices, returns, etc.