PHISON E12 SSD CONTROLLER · CVE-2026-124017 · Infrastructure
NO FIX YET
Phison E12 and E18 PCIe SSD controllers can be made to skip signature checks on firmware by writing crafted boot-patch data into an unsigned flash page. A privileged local attacker can then load unsigned firmware that persists across reinstalls and runs below the host operating system.
first public Nov 16, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Systems with an SSD built on a Phison E12 (PS5012) or E18 (PS5018) controller are exposed, and the attacker needs privileged local access to issue vendor-specific commands. VulnCheck lists the affected versions as unspecified and names no SSD models or firmware, so which drives are covered is unknown. Teams with no Phison E12 or E18 drives can skip it.
Not affected if no-phison-e12-or-e18-drive
Who cares endpoints, firmware, local-privileged, phison-e12, phison-e18, ssd
No fix yet, per the sources.
Phison E12 and E18 PCIe SSD controllers contain a Secure Boot bypass vulnerability that allows a privileged local attacker to inject persistent boot-patch tuples into the unsigned, CRC-protected flash ID page read by the BootROM. By overwriting a fuse-derived RAM variable via a crafted patch entry using Phison Vendor Specific Commands, an attacker can force CRC-only firmware verification instead of signature checking, enabling an unsigned firmware image to load and creating a persistent controller-level implant that survives firmware reinstallation and operates below the host operating system.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.